https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Fri Aug 30 11:37:41 2019
New Revision: 275098
URL: https://gcc.gnu.org/viewcvs?rev=275098=gcc=rev
Log:
Backported from mainline
2019-02-05 Jakub Jelinek
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Thu Feb 7 14:54:16 2019
New Revision: 268645
URL: https://gcc.gnu.org/viewcvs?rev=268645=gcc=rev
Log:
Backported from mainline
2019-02-05 Jakub Jelinek
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
--- Comment #4 from Jakub Jelinek ---
Author: jakub
Date: Tue Feb 5 09:17:18 2019
New Revision: 268531
URL: https://gcc.gnu.org/viewcvs?rev=268531=gcc=rev
Log:
PR target/89186
* optabs.c (prepare_cmp_insn): Pass x and y to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
--- Comment #3 from Jakub Jelinek ---
Created attachment 45595
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45595=edit
gcc9-pr89186.patch
Untested fix. If we can come up with a testcase where the memcmp needs to be
called on code that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
--- Comment #2 from Jakub Jelinek ---
I think there is a bug since r236195, emit_block_comp_via_libcall expects to be
called with the MEM arguments, rather than with XEXP (mem, 0) of those MEMs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89186
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2019-2-4
Known to work|
