https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70529
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> --- Ah that's pretty much what Manu suggested in comment 5 but without the whitespace handling, as Jakub pointed out in comment 6. Still, Manu's patch is a good start. (In reply to Manuel López-Ibáñez from comment #8) > (In reply to Axel Naumann from comment #2) > > You asked for it, so here is my wish list: > > - for C++ < 1z, do not support hexfloats, neither with "unsigned" not > > negative exponents. You can use -pedantic or -pedantic-errors for that. It might be nice if the pedantic "warning: use of C++17 hexadecimal floating constant" was controlled by -Wc++17-extensions but I'm not sure if that's possible for a preprocessor warning. It might also be nice if it called it a "hexadecimal floating-point literal", since "floating constant" is only used in C, not C++, so there's no such thing as a "C++17 hexadecimal floating constant". > Since "unsigned" exponents are supported by standard C++11, g++ has to > support them. No, as stated 0x123p1 is not valid in C++11, which is why it's a pedwarn.
