Lines Matching refs:is

5 On 32-bit Android, `off_t` is a signed 32-bit integer. This limits functions
46 aren't aware that `_FILE_OFFSET_BITS` is set. You might also have to
47 remove references to `__USE_FILE_OFFSET64` --- this is the internal
48 flag that should never be set by user code but sometimes is (by zlib,
56 #error "oops, __USE_FILE_OFFSET64 is defined"
60 In the 64-bit ABI, `off_t` is always 64-bit.
66 ## `sigset_t` is too small for real-time signals
68 On 32-bit Android, `sigset_t` is too small for ARM and x86. This means that
69 there is no support for real-time signals in 32-bit code. Android P (API
74 On 32-bit Android, `struct sigaction` is also too small because it contains
78 In the 64-bit ABI, `sigset_t` is the correct size for every architecture.
84 ## `time_t` is 32-bit on LP32 (y2038)
86 On 32-bit Android, `time_t` is 32-bit, which will overflow in 2038.
88 In the 64-bit ABI, `time_t` is 64-bit, which will not overflow until
103 ## `pthread_mutex_t` is too small for large pids
106 `/proc/sys/kernel/pid_max` is usually too small to hit our 16-bit limit,
107 but 32-bit bionic's `pthread_mutex` is a total of 32 bits, leaving just
119 entire 32-bit, and can't fail. This means that the usual "if the result is
120 between -1 and -4096, set errno and return -1" code is inappropriate for
121 these functions. Since LP32 is unlikely to be still supported long before
123 document -- this defect is actually fixable, it doesn't seem worth fixing.