[Bug c++/78620] C++11, Padding bytes not zero-intialized when POD is initialized with compiler generated default constructor

2017-06-08 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78620 Jonathan Wakely changed: What|Removed |Added Target||aarch64-linux Status|WAITI

[Bug c++/78620] C++11, Padding bytes not zero-intialized when POD is initialized with compiler generated default constructor

2016-12-01 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78620 --- Comment #3 from Jonathan Wakely --- Oops, I missed the first line off that actually does the initialization, sorry! struct tm tt1; fprintf(stderr, "no initialization\n"); print(&tt1); *That* is default-initialization (

[Bug c++/78620] C++11, Padding bytes not zero-intialized when POD is initialized with compiler generated default constructor

2016-12-01 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78620 Jonathan Wakely changed: What|Removed |Added Keywords||wrong-code Status|UNCONFIR

[Bug c++/78620] C++11, Padding bytes not zero-intialized when POD is initialized with compiler generated default constructor

2016-12-01 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78620 --- Comment #1 from Richard Biener --- AFAIK padding bytes are always having undefined content (even in C).