This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Improve PR28796 (inconsistend __builtin_nan() and __builtin_unordered()) further
- From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- To: Richard Guenther <rguenther at suse dot de>
- Cc: Roger Sayle <roger at eyesopen dot com>, gcc-patches at gcc dot gnu dot org
- Date: Sun, 03 Sep 2006 16:54:53 +0200
- Subject: Re: [PATCH] Improve PR28796 (inconsistend __builtin_nan() and __builtin_unordered()) further
- References: <Pine.LNX.4.44.0608240901140.11424-100000@www.eyesopen.com> <22750013.1156597453164.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net> <44FAD904.3070606@moene.indiv.nluug.nl> <6870909.1157294337525.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net>
Richard Guenther wrote:
There is no flag for -ffast-math. -ffast-math activates a bunch of
flags, some of which have very strict definitions, one for all the rest
(-funsafe-math-optimizations). Apart from this - what is your comment
suggesting? That -funsafe-math-optimizations is supposed to include
-ffinite-math-only? I agree that -funsafe-math-optimizations is a bad
name and should be dropped in favor of -fassociative-math -frecip-math.
I didn't like -funsafe-math-optimizations. -ffinite-math-only is a
contribution to split up the various flags that are part of -ffast-math
into a (distinct) set of flags that can have a clear definition. At
least -ffinite-math-only is OK in that respect.
I do not suggest any change yet. However, my preference would be to
split -ffast-math into sub-flags that have a definite, mathematically
sound meaning (if you know X about your program, you can apply -fflag-X
to compile it).
Cheers,
--
Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
A maintainer of GNU Fortran 95: http://gcc.gnu.org/fortran/
Who's working on GNU Fortran: http://gcc.gnu.org/2006-01/msg00000.html