Searched full:nearly (Results 1 – 25 of 225) sorted by relevance
123456789
2 May explode already nearly too large loader over the limit.
24 log_pass "Nearly-infinite recursive LUA calls fail cleanly."
17 seconds; this particular 143 mHz Ultra will drift by nearly 9 ms in that
17 * This comes nearly verbatim from:
21 # - c++17: supports full (or nearly full) C++17 programming environment.22 # - c++14: supports full (or nearly full) C++14 programming environment.23 # - c++11: supports full (or nearly full) C++11 programming environment.
55 # These values should be nearly the same with nopwrite.
15 options SMP # Nearly all v7 SoCs are multicore
51 Nearly all terminals have an audible alert
70 # mappings for nearly all the allocatable space from the first
24 * z_compress_level/z_uncompress are nearly identical copies of the
32 /// Determine whether the stack is nearly exhausted.
40 …"Setup of your $OSNAME system is nearly complete. You can now modify your configuration choices. A…
53 in the system by nearly 9%.
47 /// Returns whether the given class is nearly empty, with just virtual
39 * TRIG(x) returns trig(x) nearly rounded
71 * provide correct rounding in nearly all cases. in csqrtf()
40 * TRIG(x) returns trig(x) nearly rounded
16 # option is in opt_global.h. Nearly all the options in DEFAUlTS today are in
104 value since they are the same in nearly all cases.
266 Nearly all of the memory allocators tested made good use of memory, 268 The fastest memory allocator in the survey by nearly a factor of two457 These requests would be nearly doubled if the user-level strategy were used.
104 It is intended that nearly all of the drivers in the tree should return
326 requests rejected by the L2Q due to a full or nearly full condition which329 rejected due to a full or nearly full condition, indicating back pressure from
46 in the system by nearly 9%.