https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61281
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
Status|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61281
--- Comment #6 from Dominique d'Humieres ---
> I can confirm the misbehavior with 4.9.1, but it seems that the problem
> is gone on current trunk:
Confirmed. Likely fixed by r 216427 (pr63553).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61281
--- Comment #5 from janus at gcc dot gnu.org ---
I can confirm the misbehavior with 4.9.1, but it seems that the problem is gone
on current trunk:
$ ./a.out
rob
rob
gcc version 5.0.0 20141213 (experimental) [trunk revision 218705] (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61281
Dominique d'Humieres changed:
What|Removed |Added
CC||burnus at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61281
--- Comment #3 from Dominique d'Humieres ---
> I assume you're saying it disappeared and then reappeared and you're
> confirming
> the problem exists on the current trunk. Correct?
Sorry for the confusion. I meant
(1) I confirm the memory cor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61281
--- Comment #2 from Damian Rouson ---
I assume you're saying it disappeared and then reappeared and you're confirming
the problem exists on the current trunk. Correct?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61281
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
