Lines Matching refs:that

29 that the dynamic linker replaces with pointers to its own implementation at
35 thread-safe static initialization and the like, so it just calls functions that
42 has a `DT_INTERP` entry that says "use the following program to start me".  On
43 Android, that's either `linker` or `linker64` (depending on whether it's a
45 into memory and resolving references to symbols (so that when your code tries to
67     # Each architecture has its own subdirectory for stuff that isn't shared
68     # because it's architecture-specific. There will be a .mk file in here that
115     # because the Linux kernel interface is sufficiently different that we
117     # legacy mess that needs to be sorted out, either by replacing it with
122     # The code that implements the functionality to enable debugging of
154 that would make more sense as the place to add the wrapper.
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
171   5. Add at least basic tests. Even a test that deliberately supplies
172      an invalid argument helps check that we're generating the right symbol
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
186 Note that if you're actually just trying to expose device-specific headers to
193 This is handled by the libcore team, because they own icu, and that needs to be
200 If you make a change that is likely to have a wide effect on the tree (such as a
202 _not_ build the entire tree; just the minimum number of projects that are
204 modules will not be built. Note that `make checkbuild` will not be complete
225 Note that we use our own custom gtest runner that offers a superset of the
237 rewritten to not require root, that's an even better solution.
256 The host tests require that you have `lunch`ed either an x86 or x86_64 target.
257 Note that due to ABI limitations (specifically, the size of pthread_mutex_t),
268 As a way to check that our tests do in fact test the correct behavior (and not
280      * Note that the build system is ignorant to this flag being toggled, i.e. if