This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/20674] unexpected result from floating compare
- From: "piaget at us dot ibm dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Mar 2005 13:42:17 -0000
- Subject: [Bug middle-end/20674] unexpected result from floating compare
- References: <20050328215100.20674.piaget@us.ibm.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From piaget at us dot ibm dot com 2005-03-29 13:42 -------
(In reply to comment #10)
> Except, the value could have been spilled and reloaded from registers
> between those two source lines, which on x86, is where the problem comes
> from.
> The problem is no different simply because the *source* lines happen to
> be right next to each other.
I would have expected a compiler to identify these situations and produce code
that logically matches the code being compiled. If this is not the case, then
maybe -ffloat-store should be the default behavior with appropriate warnings
about turning -ffloat-store off.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20674