Lines Matching refs:bit

1 # 32-bit ABI bugs
3 ## 32-bit `off_t` and `_FILE_OFFSET_BITS=64`
5 On 32-bit Android, `off_t` is a signed 32-bit integer. This limits functions
28 compiled with that was actually using a 32-bit `off_t`. With a new enough NDK,
31 64-bit equivalents, and none of them (except `lseek`/`lseek64`) exist. As you
44 you'll have a 32-bit `off_t` and use the 32-bit functions. Make sure you
60 In the 64-bit ABI, `off_t` is always 64-bit.
63 in the 64-bit ABI even though they're identical to the non-`64` names.
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.
81 in the 64-bit ABI even though they're identical to the non-`64` names.
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
92 but the kernel interfaces exposed on 32-bit Android all use the 32-bit
94 do offer extra interfaces so that 32-bit processes can pass 64-bit
99 above. All apps are already required to offer 64-bit variants, and we
100 expect 64-bit-only devices within the next few years.
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