[Bug c/108531] Imaginary types are not supported, violating ISO C Annex G

2023-01-25 Thread joseph at codesourcery dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531 --- Comment #6 from joseph at codesourcery dot com --- My only real addition to my previous comments in the referenced glibc bug report is that, given we defined _Float32 which has the same "not promoted at language level in variable

[Bug c/108531] Imaginary types are not supported, violating ISO C Annex G

2023-01-25 Thread Keith.S.Thompson at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531 --- Comment #5 from Keith Thompson --- FYI, I've sent an email to the C standard editors (the addresses at the top of the N3054 draft) suggesting that imaginary number support should be optional even if __STDC_IEC_559_COMPLEX__ and

[Bug c/108531] Imaginary types are not supported, violating ISO C Annex G

2023-01-24 Thread sam at gentoo dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531 --- Comment #4 from Sam James --- LLVM side: https://github.com/llvm/llvm-project/issues/60269

[Bug c/108531] Imaginary types are not supported, violating ISO C Annex G

2023-01-24 Thread Keith.S.Thompson at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531 --- Comment #3 from Keith Thompson --- In the latest C2X draft, https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3054.pdf Annex G still requires imaginary number support for any implementation that defines __STDC_IEC_60559_COMPLEX__ or

[Bug c/108531] Imaginary types are not supported, violating ISO C Annex G

2023-01-24 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531 --- Comment #2 from Andrew Pinski --- C2x changes this ... (so does TS 18661-1 ) so

[Bug c/108531] Imaginary types are not supported, violating ISO C Annex G

2023-01-24 Thread Keith.S.Thompson at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108531 --- Comment #1 from Keith Thompson --- After I submitted this, I found that this is probably a duplicate of: https://sourceware.org/bugzilla/show_bug.cgi?id=15720 (I disagree with the resolution of that bug report.)