[Bug c++/68288] botched floating-point UDL

2021-08-07 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68288 --- Comment #5 from Andrew Pinski --- GCC, ICC, and clang all reject this. MSVC accepts this.

[Bug c++/68288] botched floating-point UDL

2020-10-11 Thread solodon at mail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68288 --- Comment #4 from Yuriy Solodkyy --- P.S. I added my previous example to this bug as they seemed to be related, feel free to split it into a separate bug if they are not. P.P.S. Change that return expression to 42_sp-p and the parser seems to

[Bug c++/68288] botched floating-point UDL

2020-10-11 Thread solodon at mail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68288 Yuriy Solodkyy changed: What|Removed |Added CC||solodon at mail dot com --- Comment #3

[Bug c++/68288] botched floating-point UDL

2015-11-12 Thread rs2740 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68288 TC changed: What|Removed |Added CC||rs2740 at gmail dot com --- Comment #1 from TC

[Bug c++/68288] botched floating-point UDL

2015-11-12 Thread lucdanton at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68288 --- Comment #2 from lucdanton at free dot fr --- (In reply to TC from comment #1) > This behavior looks correct to me. (Clang behaves identically.) > > 0e1_e+0 is a valid pp-number, so per max munch it must be parsed that way, > as a single