[Bug c/116082] -Wunterminated-string-initialization should not warn about strings that end with "\0" but should warn still for -Wc++-compat

2025-04-27 Thread steffen at sdaoden dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116082 --- Comment #13 from Steffen Nurpmeso --- I am!! *Luckily* nothing before 2010/1 (ie anything C++) uses this notation! Thank you. (godbolt.org is an interesting link, thanks.)

[Bug c/116082] -Wunterminated-string-initialization should not warn about strings that end with "\0" but should warn still for -Wc++-compat

2025-04-26 Thread steffen at sdaoden dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116082 --- Comment #11 from Steffen Nurpmeso --- I had reverted to 14.2.0. Alejandro, the NUL is not "embedded", it "terminates". *OR* at least this is what i am used to; for me this is a string literal. Also to uecker who moves the camel through the

[Bug c/116082] -Wunterminated-string-initialization should not warn about strings that end with "\0" but should warn still for -Wc++-compat

2025-04-25 Thread steffen at sdaoden dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116082 --- Comment #5 from Steffen Nurpmeso --- different to some other comments i think this is plain a bug in gcc. C99, 6.7.8 p21, and C23 is not different (here 6.7.10 p22; disclaimer: i have not truly read any standard beyond C99, though!!) want ``

[Bug c/116082] -Wunterminated-string-initialization should not warn about strings that end with "\0" but should warn still for -Wc++-compat

2025-04-25 Thread steffen at sdaoden dot eu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116082 Steffen Nurpmeso changed: What|Removed |Added CC||steffen at sdaoden dot eu --- Commen