diff options
| author | Stafford Horne <shorne@gmail.com> | 2022-09-29 15:32:39 +0100 |
|---|---|---|
| committer | Stafford Horne <shorne@gmail.com> | 2022-10-01 10:58:01 +0100 |
| commit | ca01d2526917ec6e54b30472d3aedfd46d4ca585 (patch) | |
| tree | 046f4c7aacbb00d371d9e5aad383d8848672ea8e /libgcc | |
| parent | 153ca019b7794c97972dcd291021cf074514fb3b (diff) | |
| download | gcc-ca01d2526917ec6e54b30472d3aedfd46d4ca585.zip gcc-ca01d2526917ec6e54b30472d3aedfd46d4ca585.tar.gz gcc-ca01d2526917ec6e54b30472d3aedfd46d4ca585.tar.bz2 | |
or1k: Only define TARGET_HAVE_TLS when HAVE_AS_TLS
This was found when testing buildroot with linuxthreads enabled. In
this case, the build passes --disable-tls to the toolchain during
configuration. After building the OpenRISC toolchain it was still
generating TLS code sequences and causing linker failures such as:
..../or1k-buildroot-linux-uclibc-gcc -o gpsd-3.24/gpsctl .... -lusb-1.0 -lm -lrt -lnsl
..../ld: ..../sysroot/usr/lib/libusb-1.0.so: undefined reference to `__tls_get_addr'
This patch fixes this by disabling tls for the OpenRISC target when requested
via --disable-tls.
gcc/ChangeLog:
* config/or1k/or1k.cc (TARGET_HAVE_TLS): Only define if
HAVE_AS_TLS is defined.
Tested-by: Yann E. MORIN <yann.morin@orange.com>
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions