Lines Matching refs:is

3 [bionic](https://en.wikipedia.org/wiki/Bionic_(software)) is Android's
6 This document is a high-level overview of making changes to bionic itself.
24 The dynamic linker interface library. This is actually just a bunch of stubs
26 runtime. This is where stuff like `dlopen(3)` lives.
87     # kernel. This is because ISO C and POSIX will say things like "there is
88     # a constant called PROT_NONE" or "there is a type called struct stat,
131         # This is where we keep the hacks necessary to build BSD source
137     # This is the biggest mess. The C++ files are files we own, typically
138     # because the Linux kernel interface is sufficiently different that we
167 The first question you should ask is "should I add a libc wrapper for
168 this system call?". The answer is usually "no".
170 The answer is "yes" if the system call is part of the POSIX standard.
172 The answer is probably "yes" if the system call has a wrapper in at
212      libc/include/sys/sysinfo.h is a good short example that shows the
238      your system call is exposed in <unistd.h>, for example, your test would go
243      the header file, and that the change to libc.map.txt from step 5 is
245      system call is being made.)
250      adding. Also check that external/ltp is using the libc wrapper for the
253 Some system calls are harder than others. The most common problem is a 64-bit
254 argument such as `off64_t` (a *pointer* to a 64-bit argument is fine, since
265 only purpose is to give you patterns to look for when run under strace(1).)
273 e.g. what you add in libc/libc.map.txt is:
282 The error output is:
304 As mentioned above, this is currently a two-step process:
317 This is handled by the libcore team, because they own icu, and that needs to be
324 If you make a change that is likely to have a wide effect on the tree (such as a
330 `make checkbuild` is enough.
335 The tests are all built from the tests/ directory. There is a separate
365 Currently, the list of bionic CTS tests is generated at build time by
371 Running the gtests directly is orders of magnitude faster than using CTS,
395 just the behavior we think is correct), it is possible to run the tests against
402 Another way to verify test behavior is to run against musl on the host. glibc
408 Note: the alternate OUT_DIR is used to avoid causing excessive rebuilding when