https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
--- Comment #8 from GCC Commits ---
The releases/gcc-14 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:ec43369c7e2c4b930a501252fa048df51c141970
commit r14-10870-gec43369c7e2c4b930a501252fa048df51c141970
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
--- Comment #7 from Jakub Jelinek ---
Fixed on the trunk so far.
Guess it should be eventually backported to 14/13 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:5e247ac0c28b9a2662f99c4a5420c5f7c2d0c6bd
commit r15-4736-g5e247ac0c28b9a2662f99c4a5420c5f7c2d0c6bd
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
--- Comment #3 from Jonathan Wakely ---
Yup, with optimization enabled the compiler can expand nextafter16 directly,
but for -O0 we need an extern symbol, which does not come from libstdc++
(although possibly we could define one as a weak symbol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
Andrew Pinski changed:
What|Removed |Added
See Also||https://sourceware.org/bugz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117321
--- Comment #1 from Andrew Pinski ---
I think you need libc support for full f16 support.
