- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for Fallocate (0.11 sec)
-
CHANGELOG/CHANGELOG-1.19.md
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Jan 05 05:42:32 UTC 2022 - 489.7K bytes - Viewed (0) -
lib/fips140/v1.0.0.zip
"crypto/internal/fips140/subtle" "crypto/internal/fips140deps/byteorder" "math/bits" ) type CTR struct { b Block ivlo, ivhi uint64 // start counter as 64-bit limbs offset uint64 // for XORKeyStream only } func NewCTR(b *Block, iv []byte) *CTR { // Allocate the CTR here, in an easily inlineable function, so // the allocation can be done in the caller's stack frame // instead of the heap. See issue 70499. c := newCTR(b, iv) return &c } func newCTR(b *Block, iv []byte) CTR { if len(iv) != BlockSize {...
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Wed Jan 29 15:10:35 UTC 2025 - 635K bytes - Viewed (0) -
RELEASE.md
`tf.function`-local variable: during each execution of the `tf.function`, the variable will be created and then disposed, similar to a local (i.e. stack-allocated) variable in C/C++. Currently `experimental_enable_variable_lifting=False` only works on non-XLA devices (e.g. under `@tf.function(jit_compile=False)`). * TF SavedModel:
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Mon Aug 18 20:54:38 UTC 2025 - 740K bytes - Viewed (1) -
docs/en/docs/release-notes.md
* This was reported internally by [@rushilsrivastava](https://github.com/rushilsrivastava) as a memory leak when the server had unhandled exceptions that would produce internal server errors, the memory allocated before that point would not be released. * Read the new docs: [Dependencies with `yield` and `except`](https://fastapi.tiangolo.com/tutorial/dependencies/dependencies-with-yield/#dependencies-with-yield-and-except).
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Fri Sep 05 12:48:45 UTC 2025 - 544.1K bytes - Viewed (0)