public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage
[not found] <bug-94080-4@http.gcc.gnu.org/bugzilla/>
@ 2020-03-07 19:40 ` redi at gcc dot gnu.org
2020-03-07 19:41 ` redi at gcc dot gnu.org
` (4 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2020-03-07 19:40 UTC (permalink / raw)
To: gcc-bugs
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 check if it's landed in glibc yet and resurrect that git
branch.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage
[not found] <bug-94080-4@http.gcc.gnu.org/bugzilla/>
2020-03-07 19:40 ` [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage redi at gcc dot gnu.org
@ 2020-03-07 19:41 ` redi at gcc dot gnu.org
2020-07-09 9:17 ` redi at gcc dot gnu.org
` (3 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2020-03-07 19:41 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
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/ml/gcc-bugs/2020-03/msg01320.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage
[not found] <bug-94080-4@http.gcc.gnu.org/bugzilla/>
2020-03-07 19:40 ` [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage redi at gcc dot gnu.org
2020-03-07 19:41 ` redi at gcc dot gnu.org
@ 2020-07-09 9:17 ` redi at gcc dot gnu.org
2021-01-21 9:50 ` wschmidt at gcc dot gnu.org
` (2 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2020-07-09 9:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-07-09
Ever confirmed|0 |1
Target Milestone|--- |11.0
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage
[not found] <bug-94080-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2020-07-09 9:17 ` redi at gcc dot gnu.org
@ 2021-01-21 9:50 ` wschmidt at gcc dot gnu.org
2021-04-19 9:09 ` redi at gcc dot gnu.org
2021-04-19 13:36 ` wschmidt at gcc dot gnu.org
5 siblings, 0 replies; 6+ messages in thread
From: wschmidt at gcc dot gnu.org @ 2021-01-21 9:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
--- Comment #2 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Let's see, with patches from late last year, can this be closed now?
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage
[not found] <bug-94080-4@http.gcc.gnu.org/bugzilla/>
` (3 preceding siblings ...)
2021-01-21 9:50 ` wschmidt at gcc dot gnu.org
@ 2021-04-19 9:09 ` redi at gcc dot gnu.org
2021-04-19 13:36 ` wschmidt at gcc dot gnu.org
5 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2021-04-19 9:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, I think so.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage
[not found] <bug-94080-4@http.gcc.gnu.org/bugzilla/>
` (4 preceding siblings ...)
2021-04-19 9:09 ` redi at gcc dot gnu.org
@ 2021-04-19 13:36 ` wschmidt at gcc dot gnu.org
5 siblings, 0 replies; 6+ messages in thread
From: wschmidt at gcc dot gnu.org @ 2021-04-19 13:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94080
--- Comment #4 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Thanks, Jonathan!
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-04-19 13:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-94080-4@http.gcc.gnu.org/bugzilla/>
2020-03-07 19:40 ` [Bug libstdc++/94080] -mabi=ieeelongdouble and -mfloat128 cause libstc++ header breakage redi at gcc dot gnu.org
2020-03-07 19:41 ` redi at gcc dot gnu.org
2020-07-09 9:17 ` redi at gcc dot gnu.org
2021-01-21 9:50 ` wschmidt at gcc dot gnu.org
2021-04-19 9:09 ` redi at gcc dot gnu.org
2021-04-19 13:36 ` wschmidt at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).