[Bug c++/115658] char16_t and char32_t aliasing is conserative

2024-07-25 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115658 Sam James changed: What|Removed |Added CC||jason at gcc dot gnu.org Ever confirmed

[Bug c++/115658] char16_t and char32_t aliasing is conserative

2024-06-28 Thread tom at honermann dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115658 --- Comment #3 from Tom Honermann --- In retrospect, I think I misunderstood Andrew's motivation for filing this issue. There is a difference of behavior between gcc and clang with regard to aliasing of `char16_t` and `char32_t` with respect to

[Bug c++/115658] char16_t and char32_t aliasing is conserative

2024-06-26 Thread tom at honermann dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115658 Tom Honermann changed: What|Removed |Added CC||tom at honermann dot net --- Comment #2

[Bug c++/115658] char16_t and char32_t aliasing is conserative

2024-06-25 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115658 --- Comment #1 from Andrew Pinski --- Though I should note https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2626r0.pdf and https://github.com/sg16-unicode/sg16-meetings/tree/master#may-22nd-2024 So maybe we really should keep on treat