Lines Matching refs:in

23 `cos(3)` in a separate library to save space in the days before shared
46 jump to `fopen(3)`, say, it lands in the right place).
58 ## What's in libc/?
68     # because it's architecture-specific. There will be a .mk file in here that
69     # drags in all the architecture-specific files.
87     # in external/kernel-headers/. These files must not be edited directly. The
109         # in our world. The *-compat.h files are automatically included
118     # current upstream source in one of the upstream directories or by
149 The answer is probably "yes" if the system call has a wrapper in at
153 users in different projects, and there isn't a more specific library
164      Note that you should check to see whether the constants are already in
165      kernel uapi header files, in which case you just need to make sure that
166      the appropriate POSIX header file in libc/include/ includes the
170   4. Add the function name to the correct section in libc/libc.map.txt.
173      and have the right declaration in the header file, and that you correctly
174      updated the maps in step 5. (You can use strace(1) to confirm that the
188 `TARGET_DEVICE_KERNEL_HEADERS` and friends described in [config.mk](https://android.googlesource.co…
194 updated in sync with bionic). See
228 in particular for test isolation and parallelism (both on by default).
236 we log in this case to prevent accidents!). Obviously, if the test can be
246 but in cases where you really have to run CTS:
268 As a way to check that our tests do in fact test the correct behavior (and not
282  * Set `bionic_coverage=true` in `libc/Android.mk` and `libm/Android.mk`.
295 directories, run `lcov`, and open the coverage report in your browser.
310 Bionic's test runner will run each test in its own process by default to prevent
312 running them in parallel, so they are much faster.