This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Floating point problems (accuracy).
- From: Vincent Lefevre <vincent at vinc17 dot org>
- To: Ian Lance Taylor <ian at airs dot com>
- Cc: James E Wilson <wilson at specifixinc dot com>,Phil Prentice <philp dot cheer at btinternet dot com>, mike at stec dot clara dot co dot uk,gcc-help at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Wed, 9 Feb 2005 17:50:08 +0100
- Subject: Re: Floating point problems (accuracy).
- References: <E1Cqyvy-00085r-Ad@monty-python.gnu.org> <41ED7E6E.5080905@specifixinc.com> <20050209161615.GA3300@dixsept.loria.fr> <m3ll9xlmuk.fsf@gossamer.airs.com>
On 2005-02-09 11:28:03 -0500, Ian Lance Taylor wrote:
> Try the -ffloat-store option.
Of course, this is what I do when I notice a problem (but I often
forget it).
> It's not the default because it's slows down the generated code too
> much, and most people don't care. But you raise an interesting point
> about the ISO C standard. It is possible that in strict C99 mode gcc
> should enable -ffloat-store on the x86.
and gcc shouldn't claim C conformance (via __STDC__ and
__STDC_VERSION__) when -ffloat-store is not enabled on x86.
--
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA