--- Comment #5 from jacob at jacob dot remcomp dot fr 2009-07-09 14:34
---
What do you mean by "aliasing violations" ???
Why would that code be invalid without any warning from the compiler?
It took us a lot of work for finding this bug and reporting it to you
can you explai
--- Comment #3 from jacob at jacob dot remcomp dot fr 2009-07-09 13:18
---
Created an attachment (id=18169)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18169&action=view)
script that demonstrates the bug
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40698
--- Comment #2 from jacob at jacob dot remcomp dot fr 2009-07-09 13:18
---
Created an attachment (id=18168)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18168&action=view)
Needed for linking the cpp code
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40698
--- Comment #1 from jacob at jacob dot remcomp dot fr 2009-07-09 13:17
---
Created an attachment (id=18167)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18167&action=view)
This is the cpp source needed to reproduce the bug
--
http://gcc.gnu.org/bugzilla/show_bug
--
Summary: Incorrect code generation when compiling c++ source
Product: gcc
Version: 4.3.3
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jacob at jacob dot remcomp dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40698
