This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/36953] Optimizer generates faulty assembler code when estimating max. floating point value in a for loop
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Jul 2008 13:12:17 -0000
- Subject: [Bug tree-optimization/36953] Optimizer generates faulty assembler code when estimating max. floating point value in a for loop
- References: <bug-36953-16523@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from rguenth at gcc dot gnu dot org 2008-07-28 13:12 -------
I can reproduce this with 4.2.4, but not with 4.1.3 or 4.3.1.
-fno-strict-aliasing fixes it, so I suspect it's a dup of one of the known
wrong-code
bugs with GCC 4.2.x
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |4.2.4
Known to work| |4.1.3 4.3.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36953