https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #15 from Jonathan Wakely ---
Author: redi
Date: Tue Jul 31 09:38:28 2018
New Revision: 263084
URL: https://gcc.gnu.org/viewcvs?rev=263084&root=gcc&view=rev
Log:
PR libstdc++/84654 Disable __float128 specializations for -mno-float128
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #16 from Jonathan Wakely ---
Author: redi
Date: Tue Aug 7 22:50:49 2018
New Revision: 263382
URL: https://gcc.gnu.org/viewcvs?rev=263382&root=gcc&view=rev
Log:
PR libstdc++/84654 Disable __float128 specializations for -mno-float128
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #4 from Marc Glisse ---
(In reply to Jonathan Wakely from comment #3)
> Yes it woud have been broken by r259813 and this should fix it:
I don't think that's sufficient:
- the same code is present in several files
- -Wsystem-headers -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #5 from Jonathan Wakely ---
(In reply to Marc Glisse from comment #4)
> (In reply to Jonathan Wakely from comment #3)
> > Yes it woud have been broken by r259813 and this should fix it:
>
> I don't think that's sufficient:
> - the sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #6 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #5)
> (In reply to Marc Glisse from comment #4)
> > - -Wsystem-headers -Wundef will warn
>
> That's the status quo. It would take a ton of effort to avoid -Wundef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #7 from Marc Glisse ---
(In reply to Jonathan Wakely from comment #5)
> > - -Wsystem-headers -Wundef will warn
>
> That's the status quo. It would take a ton of effort to avoid -Wundef
> warnings in libstdc++ and that's not something
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #8 from Jonathan Wakely ---
(In reply to Marc Glisse from comment #7)
> Yes, or maybe don't generate #define _GLIBCXX_USE_FLOAT128 0 but instead /*
> #undef _GLIBCXX_USE_FLOAT128 */ as we used to do and as the rest of the
> c++config.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
Jonathan Wakely changed:
What|Removed |Added
Keywords||build
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #9 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #8)
> The new logic [...] comes before the automatically added parts.
And obviously you can't #undef something that hasn't been defined yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #10 from Jonathan Wakely ---
Created attachment 44083
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44083&action=edit
Restore previous behaviour of #undef _GLIBCXX_USE_FLOAT128 based on configure
checks.
This still follows the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #11 from Marc Glisse ---
(In reply to Jonathan Wakely from comment #8)
> My autotools-fu is too weak to come up with anything better but I'd be very
> happy if you can suggest something cleaner.
For the general case, the autoconf man
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #12 from Jonathan Wakely ---
Thanks for the suggestion, it would clean up a few things in c++config so I'll
move to that next time, instead of adding another hack.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #13 from Jonathan Wakely ---
Author: redi
Date: Tue May 8 13:05:04 2018
New Revision: 260043
URL: https://gcc.gnu.org/viewcvs?rev=260043&root=gcc&view=rev
Log:
PR libstdc++/85672 #undef _GLIBCXX_USE_FLOAT128 when not supported
Rest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
Jonathan Wakely changed:
What|Removed |Added
CC||noloader at gmail dot com
--- Comment
16 matches
Mail list logo
