https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68972
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-01-14
CC| |jason at gcc dot gnu.org,
| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |5.3.0, 6.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed with today's top of trunk.
But the test doesn't seem valid. It only initializes the first element of the
VLA (using A::A(int)). The rest are initialized using the initializer-list
ctor which leaves the values of the A::i member uninitialized. It then checks
to see that the value of a[1].i is the same as the what was in the previous
VLA. Does every target guarantee that the contents of the stack will stay
unchanged or even that the two arrays will overlap?
Let me CC Jason since, AFAICT, he added the test.
