https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115658
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- 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 treating them the same. and maybe change char8_t back to similar as unsigned char ...
