[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-17 Thread bugzilla at bennee dot com
--- Comment #10 from bugzilla at bennee dot com 2007-01-17 10:35 --- (In reply to comment #9) (In reply to comment #4) Testcase compiles OK with gcc version 4.3.0 20070115 (experimental). Uh, I was compiling in 32bit mode. For x86_64 compilation fails as documented in comment #3.

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-17 Thread ubizjak at gmail dot com
--- Comment #11 from ubizjak at gmail dot com 2007-01-17 12:39 --- (In reply to comment #10) What glibc version do you have? And what platform are you building on? GNU C Library development release version 2.3.6 2.6.17-1.2142_FC4smp on i686-pc-linux-gnu and x86_64-pc-linux-gnu.

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-16 Thread bugzilla at bennee dot com
--- Comment #8 from bugzilla at bennee dot com 2007-01-16 11:28 --- (In reply to comment #7) However if the -mno-80387 option is meant to disable x87 instructions then it should be possible to build something without causing and x87 instructions to be emitted shouldn't it?

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-16 Thread ubizjak at gmail dot com
--- Comment #9 from ubizjak at gmail dot com 2007-01-17 06:58 --- (In reply to comment #4) Testcase compiles OK with gcc version 4.3.0 20070115 (experimental). Uh, I was compiling in 32bit mode. For x86_64 compilation fails as documented in comment #3. -- ubizjak at gmail dot com

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-15 Thread bugzilla at bennee dot com
--- Comment #1 from bugzilla at bennee dot com 2007-01-15 09:14 --- Created an attachment (id=12905) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12905action=view) Testcase C++ source Source code of failing example -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30470

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-15 Thread bugzilla at bennee dot com
--- Comment #2 from bugzilla at bennee dot com 2007-01-15 09:15 --- Created an attachment (id=12906) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12906action=view) --save-temps output -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30470

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-15 Thread bugzilla at bennee dot com
--- Comment #3 from bugzilla at bennee dot com 2007-01-15 09:17 --- Output of failed compile: 09:09 [EMAIL PROTECTED] [no387] g++-4.1 --save-temps -O3 -mno-80387 no387.cc /usr/include/stdlib.h: In function ‘long double strtold(const char*, char**)’: /usr/include/stdlib.h:355: error:

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-15 Thread ubizjak at gmail dot com
--- Comment #4 from ubizjak at gmail dot com 2007-01-15 15:24 --- Testcase compiles OK with gcc version 4.3.0 20070115 (experimental). -- ubizjak at gmail dot com changed: What|Removed |Added

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-15 Thread bugzilla at bennee dot com
--- Comment #6 from bugzilla at bennee dot com 2007-01-15 17:34 --- (In reply to comment #5) and this is a bug why? Well for starters why should the act of #include'ing stdlib.h cause any instructions to be emitted if strtold isn't even invoked? I don't understand exactly what the

[Bug c++/30470] Compiling C++ programs with -mno-80387 and -O3 failes

2007-01-15 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2007-01-15 17:44 --- Well for starters why should the act of #include'ing stdlib.h cause any instructions to be emitted if strtold isn't even invoked? Not really. However if the -mno-80387 option is meant to disable x87 instructions