This is the mail archive of the
mailing list for the GCC project.
Re: PowerPC Floating Point compare bug?
- To: Geoff Keating <geoffk at geoffk dot org>
- Subject: Re: PowerPC Floating Point compare bug?
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Fri, 18 May 2001 11:24:51 -0400
- cc: gcc at gcc dot gnu dot org
>>>>> Geoff Keating writes:
Geoff> I think the code simply has the wrong expansion in the movsfcc
Geoff> define_expand for this (rare) case---the operands need to be
The problem is that one cannot tell when the operands should be
treated reversed without doing another max/min pass, so it just isn't
worth it. I have removed the "NE" case from the patterns.
Geoff> That code is bad in other ways, too, it doesn't allow for overflow and
Geoff> NaNs and such.
I agree and I thought that it was conditionalized on fast-math at
one point. I would have expected that movMMcc would be conditionalized on
fast-math or when it knows the operations will be safe (as in this case
with constants and compiler-generated values).