Searched refs:never (Results 1 – 14 of 14) sorted by relevance
274 const size_t never = 512; /* never inserted elements */ in smr_shash_basic_test() local323 for (size_t i = 0; i < nelems - never; i++) { in smr_shash_basic_test()334 check_content(nelems - never); in smr_shash_basic_test()338 for (size_t i = nelems - never; i-- > 0;) { in smr_shash_basic_test()
34 lock_ticket.o_CFLAGS_ADD += -fsanitize-address-use-after-return=never
24 _leaks_ commonly occur. This happens when a reference is taken but never
276 Denotes that the kernel is locking down, this phase should never be hooked.
99 The sequence lock doesn't need to be taken for these metrics since they're never updated simultaneo…
85 Unfortunately `'type' != b'type'` and thus LLDB will never match the type when printing summaries.
39 similar fashion to `kalloc`. These functions will never fail (if the allocation65 will never fail (the kernel will instead panic if no memory can be found).363 described above. You should never use the operators on scalar types. Instead, you
91 backing nodes and the front nodes. The backing node never moves. If
43 "(iokit/common) invalid - should never be seen", // 0x001
400 * Should never be called directly by users (at least not
341 # build configs. Non-primary build configs will never compete for
99 # This is typically never specified (TARGET_CONFIGS is used)
862 // Should never get here870 // Should never get here1801 /* wait on the reply from the parent (that we will never receive) */
281 - Trying to modify a string value? You can only create new strings but never modify existing ones.