https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79455
--- Comment #6 from Martin Liška ---
Author: marxin
Date: Tue Mar 6 20:05:52 2018
New Revision: 258293
URL: https://gcc.gnu.org/viewcvs?rev=258293=gcc=rev
Log:
Backport r247342
2018-03-06 Martin Liska
Backport from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79455
--- Comment #5 from seurer at gcc dot gnu.org ---
I was hoping that fixing this on powerpc64 LE would also fix it on BE but the
issue there is slightly different. See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79455
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79455
--- Comment #3 from Martin Liška ---
Author: marxin
Date: Thu Apr 27 14:28:06 2017
New Revision: 247342
URL: https://gcc.gnu.org/viewcvs?rev=247342=gcc=rev
Log:
Fix test-case on ppc64le (PR testsuite/79455).
2017-04-27 Martin Liska
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79455
--- Comment #2 from Bill Schmidt ---
I think the most relevant issue here is that we are usually generating a call
to memset here, but apparently on rare occasions we do not. That kind of
inconsistency is troubling, to say the least.
As Segher
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79455
kelvin at gcc dot gnu.org changed:
What|Removed |Added
CC||kelvin at gcc dot gnu.org