This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/32391] Wrong code with optimization on i686-pc-linux-gnu
- From: "sunjoong at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Jun 2007 20:24:06 -0000
- Subject: [Bug fortran/32391] Wrong code with optimization on i686-pc-linux-gnu
- References: <bug-32391-14714@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #13 from sunjoong at gmail dot com 2007-06-18 20:24 -------
The '-ffloat-store' option works! Thank you.
However that gave me some quenstions;
Is that feature or bug?
There is many floating point operations of course.
Why the only one specific resion make problem?
That is not set when optimize.
So, what's the disadvantage and
why the 'fortran' with many floating point operation
dosn't take it when optimize?
Why x86 need that option but x86_64 or PPC do not need?
(In reply to comment #12)
> Do you get wrong results if you add the -ffloat-store option?
> Can you also try the -fdefault-real-8 option?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32391