https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
--- Comment #8 from Marc Glisse ---
(In reply to H.J. Lu from comment #7)
> Fixed.
Thanks HJ! Sorry for not doing it myself sooner...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
--- Comment #6 from hjl at gcc dot gnu.org ---
Author: hjl
Date: Mon Jan 12 17:08:04 2015
New Revision: 219479
URL: https://gcc.gnu.org/viewcvs?rev=219479&root=gcc&view=rev
Log:
Avoid undefined behavior in gcc.target/i386/pr64291-1.c
PR tes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
--- Comment #5 from H.J. Lu ---
(In reply to Marc Glisse from comment #4)
> Created attachment 34342 [details]
> Fixed testcase
>
> Ah, sorry, I had missed dn indeed. The attached tgz runs ok under valgrind,
> and fails the assertion with a comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
--- Comment #4 from Marc Glisse ---
Created attachment 34342
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34342&action=edit
Fixed testcase
Ah, sorry, I had missed dn indeed. The attached tgz runs ok under valgrind, and
fails the assertio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
--- Comment #3 from H.J. Lu ---
(In reply to Marc Glisse from comment #2)
> Restricting the testcase to x86_64 would be fine with me.
>
> As far as main is concerned, f could have written in n and d. The
> uninitialized values are only passed ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
--- Comment #2 from Marc Glisse ---
Restricting the testcase to x86_64 would be fine with me.
As far as main is concerned, f could have written in n and d. The uninitialized
values are only passed around, it doesn't seem relevant.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64427
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
