https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
--- Comment #4 from Bill Schmidt ---
Thanks, Jonathan!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
--- Comment #2 from Bill Schmidt ---
Let's see, with patches from late last year, can this be closed now?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
--- Comment #1 from Jonathan Wakely ---
Due to a server move, bugzilla seems to have lost the original comments on this
bug. They are archived at
https://gcc.gnu.org/ml/gcc-bugs/2020-03/msg01310.html
and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
There is a HUGE amount of work to do to make libstdc++ support it properly.
I think I've already done most of it, but last time I tried to test it
everything failed because glibc didn't have the necessary ieee long double
support yet. I should
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
Andrew Pinski changed:
What|Removed |Added
Component|c++ |libstdc++
--- Comment #1 from Andrew
