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

2020-12-10 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #12 from Jonathan Wakely --- (In reply to wuz73 from comment #11) > (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

[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 redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #10 from Jonathan Wakely --- 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 -flto.

[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 redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #8 from Jonathan Wakely --- (In reply to Martin Liška from comment #6) > I bet it's related to the construction of the s_creator and its usage at > moduleB.cpp:8 > It's likely Static Initialization Order Fiasco: >

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

2020-12-10 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 Martin Liška changed: What|Removed |Added Resolution|--- |INVALID Status|NEW

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

2020-12-10 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 Martin Liška changed: What|Removed |Added CC||redi at gcc dot gnu.org --- Comment #6

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

2020-12-10 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 Martin Liška changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[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

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

2020-12-10 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #3 from Martin Liška --- Hello. The attached libraries are not what we can use as a reproducer: https://www.gnu.org/software/gcc/bugs/

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

2020-12-10 Thread wuz73 at hotmail dot com via Gcc-bugs
: [Bug c++/98220] LTO causes floating point exception https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #1 from Andrew Pinski --- Are you sure this just not a divide by zero? On x86, an integer divide by zero will throw an FPU exception. -- You are receiving this mail because: You

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

2020-12-10 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98220 --- Comment #1 from Andrew Pinski --- Are you sure this just not a divide by zero? On x86, an integer divide by zero will throw an FPU exception.