riables fixes it.
--
Summary: Optimizer problem with aliasing floating point variable
Product: gcc
Version: 3.4.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot or
--- Additional Comments From bobm75 at gmail dot com 2005-03-02 00:33
---
I read the documentation on -fstrict-aliasing and it makes sense to me why this
code breaks those rules. I just wonder why the compiler didn't warn about it,
since this seems to be a pretty straight forward
--- Additional Comments From bobm75 at gmail dot com 2005-03-02 18:03
---
Ok, thank you for your explanation. We have a huge codebase and we just
increased the optimization level from -O to -O2 (together with -march=pentium3),
that's when this came up. Since most of this code has
ion
pointer
Product: gcc
Version: 3.3.6
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bobm75 at gmail dot com
CC: gcc-bugs at
