Searched refs:exact (Results 1 – 7 of 7) sorted by relevance
| /bionic/libc/upstream-openbsd/lib/libc/gdtoa/ |
| D | strtodg.c | 178 (d, fpi, exp, bits, exact, rd, irv) in rvOK() argument
179 U *d; FPI *fpi; Long *exp; ULong *bits; int exact, rd, *irv; in rvOK()
181 (U *d, FPI *fpi, Long *exp, ULong *bits, int exact, int rd, int *irv)
197 if (exact)
204 exact &&
225 if (!exact)
278 if (!lostbits && !exact)
|
| /bionic/libc/malloc_debug/ |
| D | README_marshmallow_and_earlier.md | 58 Note: If multiple allocations have the same exact backtrace, then only one
|
| D | README.md | 220 Android devices). The best way to see the exact signal being used is to
|
| /bionic/docs/ |
| D | status.md | 418 whatever build system they're using. The exact subset of FORTIFY available to
|
| D | elf-tls.md | 406 > question therefore is the exact field layouts required. Happily, the implementors of libpthread
|
| /bionic/ |
| D | README.md | 222 need to understand by using the exact same wording where possible).
|
| D | android-changes-for-ndk-developers.md | 294 it is not present in that exact location on the device.
|