https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
acsawdey at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #10 from acsawdey at gcc dot gnu.org ---
Author: acsawdey
Date: Sat Feb 9 17:11:06 2019
New Revision: 268725
URL: https://gcc.gnu.org/viewcvs?rev=268725&root=gcc&view=rev
Log:
2019-02-09 Aaron Sawdey
Backported from mainl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #9 from acsawdey at gcc dot gnu.org ---
The fixes for this are in trunk now. I will backport to gcc-8-branch in a week
and then this can be closed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #8 from acsawdey at gcc dot gnu.org ---
Author: acsawdey
Date: Tue Feb 5 16:32:06 2019
New Revision: 268547
URL: https://gcc.gnu.org/viewcvs?rev=268547&root=gcc&view=rev
Log:
2019-02-05 Aaron Sawdey
PR target/89112
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #7 from acsawdey at gcc dot gnu.org ---
Author: acsawdey
Date: Tue Feb 5 16:30:45 2019
New Revision: 268546
URL: https://gcc.gnu.org/viewcvs?rev=268546&root=gcc&view=rev
Log:
2019-02-05 Aaron Sawdey
PR target/89112
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #6 from Segher Boessenkool ---
The patch in #c5 is pre-approved everywhere. Thanks!
#c4... Do you *want* to keep it together? Is it in fact cold? If it is not,
maybe you can improve the execution estimate for it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #5 from acsawdey at gcc dot gnu.org ---
This patch fixes the issue on trunk:
Index: gcc/config/rs6000/rs6000.md
===
--- gcc/config/rs6000/rs6000.md (revision 268403)
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #4 from acsawdey at gcc dot gnu.org ---
Well I can't blame this one on the linker or optimization. The splitting for
the case where the branch destination is too far is wrong in tf_:
static char seq[96];
char *bcs = output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #3 from acsawdey at gcc dot gnu.org ---
It appears that gcc decided to split the bdnzt generated by the memcmp
expansion because the destination was out of range, and produced this:
bdz $+12
beq 0,$+8
b $+8;b .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #2 from acsawdey at gcc dot gnu.org ---
I'm seeing this on both gcc-8-branch and trunk, but only with -mcpu=power9.
I'll figure out what happened here and get it fixed in trunk then back ported
to 8.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
acsawdey at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89112
--- Comment #1 from Samuel Holland ---
Created attachment 45563
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45563&action=edit
Output of gcc -v
12 matches
Mail list logo
