diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2025-05-20 09:36:58 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-05-20 09:36:58 +0200 |
| commit | 35fd4abd3b9631e24f8b0b910edb001561eaa382 (patch) | |
| tree | 79cb1683c9e025a6db0628e7ec1bbe9e95b850a8 /gcc/testsuite/gcc.target/riscv/sat/sat_u_add-run-1-u64.c | |
| parent | e38027c8ff449ffadaca449004bb891b9094ad00 (diff) | |
| download | gcc-master.zip gcc-master.tar.gz gcc-master.tar.bz2 | |
When adding _BitInt support I was hoping all or most of arches would
implement it already for GCC 14. That didn't happen and with
new hosts adding support for _BitInt for GCC 16 (s390x-linux and as was
posted today loongarch-linux too), we need the _BitInt support functions
exported on those arches at GCC_16.0.0 rather than GCC_14.0.0 which
shouldn't be changed anymore.
The following patch does that. Both arches were already exporting
some of the _BitInt related symbols in their specific map files, this
just moves the remaining ones there as well.
2025-05-20 Jakub Jelinek <jakub@redhat.com>
* libgcc-std.ver.in (GCC_14.0.0): Remove bitint related exports
from here.
* config/i386/libgcc-glibc.ver (GCC_14.0.0): Add them here.
* config/i386/libgcc-darwin.ver (GCC_14.0.0): Likewise.
* config/i386/libgcc-sol2.ver (GCC_14.0.0): Likewise.
* config/aarch64/libgcc-softfp.ver (GCC_14.0.0): Likewise.
Diffstat (limited to 'gcc/testsuite/gcc.target/riscv/sat/sat_u_add-run-1-u64.c')
0 files changed, 0 insertions, 0 deletions