Lines Matching refs:that

6 that use `off_t` to working on files no larger than 2GiB.
20 all you need are functions like `read` that don't take/return `off_t`, large
28 compiled with that was actually using a 32-bit `off_t`. With a new enough NDK,
30 all functions that take an `off_t` become unavailable. You've asked for their
35 [linker map](libc/libc.map.txt) for full details. Note also that in NDK r16 and
38 that's often needed. This means that code using `_FILE_OFFSET_BITS=64`
39 and `mmap` (but no other functions that are unavailable at your target
46 aren't aware that `_FILE_OFFSET_BITS` is set. You might also have to
48 flag that should never be set by user code but sometimes is (by zlib,
50 doesn't compile, you can insert this just before the line that's failing
68 On 32-bit Android, `sigset_t` is too small for ARM and x86. This means that
71 that takes a `sigset_t` (so `sigprocmask64` takes a `sigset64_t` where
94 do offer extra interfaces so that 32-bit processes can pass 64-bit
109 mutexes for tids that don't fit in 16 bits. This typically manifests as