https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Wed Nov 9 16:21:45 2016
New Revision: 242007
URL: https://gcc.gnu.org/viewcvs?rev=242007=gcc=rev
Log:
PR target/77718
* builtins.c (expand_builtin_memcmp): Formatting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
--- Comment #6 from acsawdey at gcc dot gnu.org ---
I can confirm that Bernd's patch fixes the issue, bootstraps on powerpc64le,
and does not cause any new regression test failures in "make check".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
--- Comment #5 from Aaron Sawdey ---
On Tue, 2016-09-27 at 14:30 +, bernds at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
>
> --- Comment #4 from Bernd Schmidt ---
> So something like this maybe?
>
> Index:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
--- Comment #4 from Bernd Schmidt ---
So something like this maybe?
Index: builtins.c
===
--- builtins.c (revision 240511)
+++ builtins.c (working copy)
@@ -3707,11 +3707,13 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
--- Comment #3 from acsawdey at gcc dot gnu.org ---
Bernd,
I identified the problem on powerpc64le. I think it may not show up on x86_64
because of differences in how builtin memcmp gets expanded. Normally this is
hidden because if both strings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
--- Comment #2 from Bernd Schmidt ---
Over here the testcase seems not to arrive in this function, and it prints the
same value (-5) twice, which I think is supposed to be expected?
Please clarify.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77718
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
