This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: optimization/4231
- To: bh at techhouse dot org, gcc-gnats at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Subject: Re: optimization/4231
- From: Benoit Hudson <bh at techhouse dot org>
- Date: Tue, 04 Sep 2001 19:51:45 -0400
Turns out this is because gcc stores maxgrade in memory as a 64-bit
double, then loads it again, so that
maxgrade=grade
no longer implies
maxgrade==grade
On the other hand, the optimizer might be expected to solve this.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4231&database=gcc