tequilaOS/platform_bionic
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge "Clarify the defines documentation further." am: 1441748956

Browse source 
Original change: https://android-review.googlesource.com/c/platform/bionic/+/2595593

Change-Id: I63a08af3dc8e9e8f6a63706cbae36ba2a72d3212
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
Treehugger Robot 2023-05-18 20:05:32 +00:00 committed by Automerger Merge Worker
commit 17b5bb88c1
1 changed files with 13 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/defines.md
View file

@ -54,13 +54,19 @@ If your code can be built with a variety of different NDK versions, and needs to
work around issues with some of them, use these macros to detect the versinon of work around issues with some of them, use these macros to detect the versinon of
the NDK you're being built with. Usually only `__NDK_MAJOR__` will be necessary. the NDK you're being built with. Usually only `__NDK_MAJOR__` will be necessary.
## `__arm__`, `__aarch64__`, `__i386__`, `__x86_64__`, `__riscv` ## `__arm__`/`__aarch64__`, `__i386__`/`__x86_64__`, `__riscv`
If your code is specific to a particular processor architecture, use these If your code is specific to a particular processor architecture, use
macros to conditionally compile. Note that the ABI usually called `arm64` uses these macros to conditionally compile. Note that the ABI usually called
the macro `__aarch64__` and the ABI usually called `x86` uses `__i386__`. `arm64` uses the macro `__aarch64__` and the ABI usually called `x86` uses
`__i386__`. Android only supports riscv64, so `__riscv` is a sufficient
check for Android-only code. If you need to write code portable to other
operating systems that do support riscv32, you'll also need to check
whether `__riscv_xlen` is 32 or 64.
## `__LP32__` and `__LP64__` ## `__ILP32__` and `__LP64__`
If your code depends on "bitness" -- whether `long` and pointers are 32- or If your code depends on "bitness" -- whether `long` and pointers are 32-
64-bit -- use these macros to conditionally compile. or 64-bit -- use these macros to conditionally compile. Note the extra
"I" in the 32-bit macro (since `int`, `long`, and pointers are all 32-bit
on such systems, with `long long` being needed for a 64-bit type).