[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2014-02-16 Thread jackie.rosen at hushmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30111 Jackie Rosen jackie.rosen at hushmail dot com changed: What|Removed |Added CC|

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2009-02-11 Thread jason at gcc dot gnu dot org
--- Comment #9 from jason at gcc dot gnu dot org 2009-02-11 22:38 --- Subject: Bug 30111 Author: jason Date: Wed Feb 11 22:38:37 2009 New Revision: 144112 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=144112 Log: PR c++/30111 * init.c (build_value_init_noctor):

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2009-02-11 Thread jason at gcc dot gnu dot org
--- Comment #10 from jason at gcc dot gnu dot org 2009-02-11 22:50 --- Fixed for 4.4. -- jason at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2008-02-04 Thread rguenth at gcc dot gnu dot org
--- Comment #8 from rguenth at gcc dot gnu dot org 2008-02-04 16:06 --- Jason is this the same issue as PR33916 you fixed? (Your fix didn't change the outcome of this PR though) -- rguenth at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2007-06-17 Thread jwakely dot gcc at gmail dot com
--- Comment #7 from jwakely dot gcc at gmail dot com 2007-06-18 01:36 --- Confirmed on x86-linux, sparc-solaris and ppc-AIX so I've removed the Target. Also verified that valgrind shows the uninitialised memory reads. This bug breaks common idioms like: template typename A, typename

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2007-06-09 Thread pinskia at gcc dot gnu dot org
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-06-10 02:18 --- *** Bug 32141 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2006-12-30 Thread gdr at gcc dot gnu dot org
--- Comment #5 from gdr at gcc dot gnu dot org 2006-12-30 19:40 --- Thsi is indeed a bug in g++. the pod() in inherit() is a value-initialization, not a call to default-constructor. -- gdr at gcc dot gnu dot org changed: What|Removed |Added

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2006-12-08 Thread gcc-bugzilla at kayari dot org
--- Comment #4 from gcc-bugzilla at kayari dot org 2006-12-08 10:36 --- Richard, there's no difference between pod() and p() in this case, both are value-initialisations of a POD class, therefore all non-static data members should be value-initialised. I cited 8.5p5 for good reason :)

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2006-12-07 Thread gcc-bugzilla at kayari dot org
--- Comment #1 from gcc-bugzilla at kayari dot org 2006-12-07 18:03 --- Values printed out confirm it on Linux for 3.3.5 20050117 (prerelease) (SUSE Linux), and official FSF 3.4.3, 4.0.1, 4.0.2, 4.1.1 N.B. I meant AIX 5.3, not 5/3 --

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2006-12-07 Thread rguenth at gcc dot gnu dot org
--- Comment #2 from rguenth at gcc dot gnu dot org 2006-12-08 07:27 --- As compose is not POD it initializes p in the constructor. For inherit the constructor of p is called which - surprise - as a POD constructor does nothing. -- rguenth at gcc dot gnu dot org changed:

[Bug c++/30111] Value-initialization of POD base class doesn't initialize members

2006-12-07 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-12-08 07:34 --- (In reply to comment #2) As compose is not POD it initializes p in the constructor. For inherit the constructor of p is called which - surprise - as a POD constructor does nothing. Actually read the standard,