https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
--- Comment #7 from Jonathan Wakely ---
There's a related (but slightly different) problem for F128 suffixes:
auto f = __FLT128_MIN__;
f128.C:1:10: error: unable to find numeric literal operator ‘operator""F128’
The macros for the F128 constan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
Jonathan Wakely changed:
What|Removed |Added
CC||redi at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
--- Comment #5 from Eric Gallager ---
(In reply to Manuel López-Ibáñez from comment #4)
> (In reply to Jonathan Wakely from comment #2)
> > (In reply to Patrick J. LoPresti from comment #0)
> > > Note that my code does not use any quad-precision
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
--- Comment #3 from Patrick J. LoPresti ---
Yes, is an extension. But it would be nice, IMO, if it were a
standard-compatible extension.
So this is, as you say, a feature request somehow to enable quad-precision
literals in standard compilation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
--- Comment #1 from Jonathan Wakely ---
This is not a bug. If you want to use the non-standard extensions in
then either use -std=gnu++11 instead of -std=c++11, or use
-fext-numeric-literals to enable the non-standard suffixes, as suggested.
Us
