[Bug debug/117647] New: Setting break point changes program output

2024-11-18 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117647 Bug ID: 117647 Summary: Setting break point changes program output Product: gcc Version: 8.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debu

[Bug c++/106542] -O2 sign-extended uint32 to uint64

2022-08-05 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106542 wuz73 at hotmail dot com changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLV

[Bug tree-optimization/99536] unexplained warning on "uninitialized value" in std::normal_distribution

2022-08-05 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99536 wuz73 at hotmail dot com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2022-08-05 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 99536, which changed state. Bug 99536 Summary: unexplained warning on "uninitialized value" in std::normal_distribution https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99536 What|Removed |

[Bug c++/106542] New: -O2 sign-extended uint32 to uint64

2022-08-05 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106542 Bug ID: 106542 Summary: -O2 sign-extended uint32 to uint64 Product: gcc Version: 9.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/99536] New: unexplained warning on "uninitialized value"

2021-03-10 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99536 Bug ID: 99536 Summary: unexplained warning on "uninitialized value" Product: gcc Version: 5.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/98220] LTO causes floating point exception

2020-12-10 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #11 from wuz73 at hotmail dot com --- (In reply to Jonathan Wakely from comment #10) > No it's, not a bug, because the C++ standard says the order is unspecified. > The compiler is allowed to reorder them, and that's what happens with

[Bug c++/98220] LTO causes floating point exception

2020-12-10 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #9 from wuz73 at hotmail dot com --- Without -flto I can specify link order. So -flto will ignore the order? It is still a bug as in many cases orders do matter.

[Bug c++/98220] LTO causes floating point exception

2020-12-10 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #4 from wuz73 at hotmail dot com --- In the attached test case, there is a makefile and source code. Here's the output without -flto: $ make g++ -std=c++11 -Wall -g -O2 -o main.o -c main.cpp g++ -std=c++11 -Wall -g -O2 -o module.o -c

[Bug c++/98220] LTO causes floating point exception

2020-12-10 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #2 from wuz73 at hotmail dot com --- There's no division as can be seen in the test case. From: pinskia at gcc dot gnu.org Sent: Thursday, December 10, 2020 4:19 PM To: wu...@hotmail.com Subject: [Bug

[Bug c++/98220] New: LTO causes floating point exception

2020-12-10 Thread wuz73 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 Bug ID: 98220 Summary: LTO causes floating point exception Product: gcc Version: 9.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++