[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:

[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,

[Bug c++/111897] New: 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 Bug ID: 111897 Summary: Initialization of _Float16 with f.p. constant gives false warning Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/108920] Condition falsely optimized out

2023-02-25 Thread agner at agner dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108920 Agner Fog changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug middle-end/108920] Condition falsely optimized out

2023-02-24 Thread agner at agner dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108920 --- Comment #3 from Agner Fog --- It seems to work with gcc 9.4.0. Thank you

[Bug c++/108920] New: Condition falsely optimized out

2023-02-24 Thread agner at agner dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108920 Bug ID: 108920 Summary: Condition falsely optimized out Product: gcc Version: 9.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++