diff options
| author | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2023-12-04 10:52:52 +0000 |
|---|---|---|
| committer | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2023-12-08 11:29:06 +0000 |
| commit | dbbfb52b0e9c66ee9d05b8fd17c4f44655e48463 (patch) | |
| tree | 701027cd38d86213b29d683c599ef168edc41fda /gcc | |
| parent | 3ebb591c65b4fbe0cddd23ebc0ca2d9f7aef2cec (diff) | |
| download | gcc-dbbfb52b0e9c66ee9d05b8fd17c4f44655e48463.zip gcc-dbbfb52b0e9c66ee9d05b8fd17c4f44655e48463.tar.gz gcc-dbbfb52b0e9c66ee9d05b8fd17c4f44655e48463.tar.bz2 | |
libgcc: aarch64: Configure check for __getauxval
Add configure check for the __getauxval ABI symbol, which is always
available on aarch64 glibc, and may be available on other linux C
runtimes. For now only enabled on glibc, others have to override it
target_configargs=libgcc_cv_have___getauxval=yes
This is deliberately obscure as it should be auto detected, ideally
via a feature test macro in unistd.h (link time detection is not
possible since the libc may not be installed at libgcc build time),
but currently there is no such feature test mechanism.
Without __getauxval, libgcc cannot do runtime CPU feature detection
and has to assume only the build time known features are available.
libgcc/ChangeLog:
* config.in: Undef HAVE___GETAUXVAL.
* configure: Regenerate.
* configure.ac: Check for __getauxval.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions