http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57019



--- Comment #5 from janus at gcc dot gnu.org 2013-04-21 15:23:49 UTC ---

I can confirm a runtime segfault (invalid memory reference) on comment 4 with

4.7, 4.8 and trunk.



With 4.3 one does not get a segfault, but the output is



   99.0000000       99.0000000       99.0000000    

   88.0000000       99.0000000       99.0000000



which means that the assignment really only sets v(1).



So there is already a wrong-code issue in 4.3, but the segfault itself is a

regression (which might be connected to the other one, see comment 2).

Reply via email to