Searched full:tricky (Results 1 – 25 of 390) sorted by relevance
12345678910>>...16
56 # edge cases, see directive-for-escape.mk. Adding another such tricky detail107 # Another tricky detail are nested .for loops in a single file that use the
9 # Using the dollar sign in variable names is tricky and not recommended.
63 # This is tricky to measure correctly since there are many inconsistencies
5 * which is otherwise tricky with compilers that don't support -c and -o
18 * when casting pointers. The impact is tricky: on machines where
17 not handle tricky code correctly.
11 * that are tricky to compile twice. It also reduces the number of ifdefs we
7 # and an inline expansion in case somebody gets tricky
42 ** stream should now be closed. This is a tricky way to test
89 /* Check that 1 <= plane <= 16. Tricky optimized form of: */
21 * Internal word types. Somewhat tricky. This could be decided separately per
12 # Getting comments into the output is tricky; we turn C++-style // comments
13 dnl Does *not* test for __visibility__("protected") - which has tricky
76 # The escape code for 'FAULTED' is a little more tricky. The line starts like
144 Debug output can be very noisy, and it can be tricky
482 is a bit tricky.511 (Yes, this is a bit tricky, but it's a standard idiom.)
122 * The last part is especially tricky and currently has limited234 * arguments are a bit tricky; see the code in genacl.c.
56 // tricky to implement. Could use std::to_chars.
6 Tickadj is a bit more tricky because of the behaviour of adjtime(),
50 * The __CONCAT macro is a bit tricky -- make sure you don't put spaces
79 nfsmmap Some tests to exercise some tricky cases in NFS and mmap
51 // stuff. this will be a little tricky and we may need to expand
38 * tricky... The extern variable suboptarg is a pointer to the token
150 Creating effective process sandboxes is a tricky process that involves
67 // This is a bit tricky. If we just call readBytes, we are requiring that it in writeStreamRef()