[Bug c++/111897] Initialization of _Float16 with f.p. constant gives false warning

2023-10-25 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111897 Jonathan Wakely changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRME

[Bug c++/111897] Initialization of _Float16 with f.p. constant gives false warning

2023-10-25 Thread agner at agner dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111897 --- Comment #3 from Agner Fog --- I have asked the authors of the linked document. They say that the example in the document is wrong. The latest version still has the error in the example: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/202

[Bug c++/111897] Initialization of _Float16 with f.p. constant gives false warning

2023-10-20 Thread agner at agner dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111897 --- Comment #2 from Agner Fog --- Thank you Jonathan. The problem is that the C++ standard is becoming so complicated that nobody can master it, not even the persons who wrote the example in the proposal. `_Float16 A{1.0};` gives a warning, wh

[Bug c++/111897] Initialization of _Float16 with f.p. constant gives false warning

2023-10-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111897 Jonathan Wakely changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment