diff options
| author | Joseph Myers <josmyers@redhat.com> | 2024-11-19 22:25:39 +0000 |
|---|---|---|
| committer | Joseph Myers <josmyers@redhat.com> | 2024-11-19 22:25:39 +0000 |
| commit | d899b48a30b2dd27ab25e1cd90ce28b75f7c0755 (patch) | |
| tree | 1be86f8647ba0578872b9f5515c32f76a6777136 /sysdeps/riscv/rvf/s_fpclassifyf.c | |
| parent | 3ef7e4286155b70816c2393414b935751a39d685 (diff) | |
| download | glibc-master.zip glibc-master.tar.gz glibc-master.tar.bz2 | |
Two of the architecture bits/fenv.h headers define femode_t if
__GLIBC_USE (IEC_60559_BFP_EXT), instead of the correct condition
__GLIBC_USE (IEC_60559_BFP_EXT_C23) (both were added after commit
0175c9e9be5f0b2000859666b6e1ef3696f1123b, but were probably first
developed before it and then not updated to take account of its
changes). This results in failures of the installed headers check for
fenv.h when building with GCC 15 (defaults to -std=gnu23 - we don't
yet have an installed-headers test specifically for C23 mode and don't
yet require a compiler with such a mode for building glibc) together
with a combination of options leaving C23 features enabled, since the
declarations of functions using femode_t use the correct conditions;
see
<https://sourceware.org/pipermail/libc-testresults/2024q4/013163.html>.
Fix the conditionals to get <fenv.h> to work correctly in C23 mode
again.
Tested with build-many-glibcs.py (arc-linux-gnu, arch-linux-gnuhf,
or1k-linux-gnu-hard, or1k-linux-gnu-soft).
Diffstat (limited to 'sysdeps/riscv/rvf/s_fpclassifyf.c')
0 files changed, 0 insertions, 0 deletions