This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/9736] same fp comparison can lead to different results


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9736



------- Additional Comments From pinskia at physics dot uc dot edu  2003-08-22 01:41 -------
Subject: Re:  same fp comparison can lead to different results

> ------- Additional Comments From timothyprince at sbcglobal dot net  2003-08-22 01:37 -------
> Subject: Re:  same fp comparison can lead to different results
> 
> On Thursday 21 August 2003 17:41, pinskia at gcc dot gnu dot org wrote:
> 
> > 00:41 ------- This is really the same as bug 323 and is being discussed on
> > the mailing lists today, the only way to fix this is to slow down your
> > program via having -ffloat-store being default on x86. The other way to fix
> > this is get rid of x86 support which is not going to happen. Moving this to
> > the target componet because that is where it belongs as this is a x86
> > problem only.
> >
> > I am going to go on a limb now and say if you want the correct (by what the
> > standard says) floating point results do not use x86, use something else.
> There are additional possibilities.  Use -mfpmath=sse -march=pentium[34] 
> according to your CPU; if necessary, set the precision mode in accordance 
> with your desires.  I haven't seen such discussions lately, but if the FAQ's 
> remain out of date, point me to them and I'll suggest patches.
The thread start here <http://gcc.gnu.org/ml/gcc/2003-08/msg01183.html>.
It is a long one though which discusses what the problems are and what will happen if this gets fixed via GCC.

Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]