[Bug c++/77572] wrong value for extended ASCII characters in diagnostics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77572 --- Comment #3 from Eric Gallager --- (In reply to Jonathan Wakely from comment #2) > I still get the same output as Martin using recent trunk, and any older > versions. Ah, I see what happens, I get the same nonsensical output as Martin when I compile for 64-bit, but when I compile for 32-bit, I get the normal-looking output I got before: $ g++ -m64 -c -S -Wall 77572.cc 77572.cc:1:19: error: invalid conversion from 'const char*' to 'int' [-fpermissive] constexpr int i = "\x0_\x01_\x7f_\x80_\xff"; ^ 77572.cc:1:19: error: '(int)((const char*)"\000_\001_\177_\3777600_\377")' is not a constant expression $ g++ -m32 -c -S -Wall 77572.cc 77572.cc:1:19: error: invalid conversion from 'const char*' to 'int' [-fpermissive] constexpr int i = "\x0_\x01_\x7f_\x80_\xff"; ^ 77572.cc:1:19: error: conversion from pointer type 'const char (*)[10]' to arithmetic type 'int' in a constant expression $
[Bug c++/77572] wrong value for extended ASCII characters in diagnostics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77572 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2017-08-29 Ever confirmed|0 |1 --- Comment #2 from Jonathan Wakely --- I still get the same output as Martin using recent trunk, and any older versions.
[Bug c++/77572] wrong value for extended ASCII characters in diagnostics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77572 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment #1 from Eric Gallager --- The output I get doesn't have the nonsensical escape sequences: $ /usr/local/bin/g++ -c -S -Wall 77572.cc 77572.cc:1:19: error: invalid conversion from ‘const char*’ to ‘int’ [-fpermissive] constexpr int i = "\x0_\x01_\x7f_\x80_\xff"; ^ 77572.cc:1:19: error: conversion from pointer type ‘const char (*)[10]’ to arithmetic type ‘int’ in a constant expression $ So, FIXED? (You're usually better than me at narrowing down the revision when the fix happened so I'll leave that to you)