[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2009-03-30 Thread jsm28 at gcc dot gnu dot org
--- Comment #18 from jsm28 at gcc dot gnu dot org 2009-03-30 21:50 --- Closing 4.2 branch, fixed in 4.3. -- jsm28 at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2008-05-19 Thread jsm28 at gcc dot gnu dot org
--- Comment #17 from jsm28 at gcc dot gnu dot org 2008-05-19 20:23 --- 4.2.4 is being released, changing milestones to 4.2.5. -- jsm28 at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2008-02-01 Thread jsm28 at gcc dot gnu dot org
--- Comment #16 from jsm28 at gcc dot gnu dot org 2008-02-01 16:54 --- 4.2.3 is being released now, changing milestones of open bugs to 4.2.4. -- jsm28 at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2007-10-09 Thread mmitchel at gcc dot gnu dot org
--- Comment #15 from mmitchel at gcc dot gnu dot org 2007-10-09 19:20 --- Change target milestone to 4.2.3, as 4.2.2 has been released. -- mmitchel at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2007-10-03 Thread jason at gcc dot gnu dot org
--- Comment #14 from jason at gcc dot gnu dot org 2007-10-04 01:29 --- Both bug32182 and test_4 work for me with pre-4.3.0 on i686-pc-linux-gnu, so I'm going to set known to work for 4.3. -- jason at gcc dot gnu dot org changed: What|Removed

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2007-07-19 Thread mmitchel at gcc dot gnu dot org
-- mmitchel at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.2.1 |4.2.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32182

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2007-07-03 Thread mmitchel at gcc dot gnu dot org
-- mmitchel at gcc dot gnu dot org changed: What|Removed |Added Priority|P3 |P1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32182

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2007-06-04 Thread rguenth at gcc dot gnu dot org
-- rguenth at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.2.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32182

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2007-06-02 Thread rguenth at gcc dot gnu dot org
--- Comment #12 from rguenth at gcc dot gnu dot org 2007-06-02 11:35 --- Confirmed. Actually compiling Wrapper.cxx with -fstrict-aliasing is enough to trigger the failure. In getItem() the difference is bb 2: - D.3769 = _local_result + 4B; - this = (struct BaseClass *) D.3769; -

[Bug c++/32182] [4.2 Regression] -fstrict-aliasing optimizations cause constructor not to run for object causing segfault

2007-06-02 Thread rguenth at gcc dot gnu dot org
--- Comment #13 from rguenth at gcc dot gnu dot org 2007-06-02 11:45 --- It looks like 12.6.2/5-6 specify it enough to make the testcase valid. The BaseClass is only once initialized by the most derived object initializer specification. --