Searched refs:never (Results 1 – 21 of 21) sorted by relevance
285 const size_t never = 512; /* never inserted elements */ in smr_shash_basic_test() local334 for (size_t i = 0; i < nelems - never; i++) { in smr_shash_basic_test()345 check_content(nelems - never); in smr_shash_basic_test()349 for (size_t i = nelems - never; i-- > 0;) { in smr_shash_basic_test()
41 lock_ticket.o_CFLAGS_ADD += -fsanitize-address-use-after-return=never
26 _leaks_ commonly occur. This happens when a reference is taken but never
41 similar fashion to `kalloc`. These functions will never fail (if the allocation67 will never fail (the kernel will instead panic if no memory can be found).378 described above. You should never use the operators on scalar types. Instead, you
68 - task ports are never unpinned;
227 there is never auxiliary data in this form.
130 destroyed. Pinned ports must never have a send right count going to zero in a473 Some of the exceptions are never fatal (hitting them will only emit a simulated
54 never use `str` functions to write to strings. Functions that simply read250 `strn` functions are **never** recommended. You should use `strbuflen` over
312 Denotes that the kernel is locking down, this phase should never be hooked.
91 backing nodes and the front nodes. The backing node never moves. If
43 "(iokit/common) invalid - should never be seen", // 0x001
111 The sequence lock doesn't need to be taken for these metrics since they're never updated simultaneo…
209 value stashed in the new thread's SME state. If the new process has never used217 which never has `ZA` state.
195 checks are never desirable, it is better to catch them at that stage than at any
105 - Speculative Queue: file-backed pages which have never been activated. These
327 watchOS. These kernels respond to these MIG messages but Libsystem never sends
348 # build configs. Non-primary build configs will never compete for
99 # This is typically never specified (TARGET_CONFIGS is used)
400 * Should never be called directly by users (at least not
286 - Trying to modify a string value? You can only create new strings but never modify existing ones.
945 // Should never get here953 // Should never get here1916 /* wait on the reply from the parent (that we will never receive) */