https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
--- Comment #8 from Steve Kargl ---
On Wed, Dec 07, 2016 at 01:31:51AM +, dmalcolm at gcc dot gnu.org wrote:
>
> --- Comment #7 from David Malcolm ---
> Sorry about the breakage. Should be fixed by r243332.
>
Thanks for the prompt attent
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
--- Comment #6 from David Malcolm ---
Author: dmalcolm
Date: Wed Dec 7 01:28:13 2016
New Revision: 243332
URL: https://gcc.gnu.org/viewcvs?rev=243332&root=gcc&view=rev
Log:
Fix x86_64-ism in selftest (PR bootstrap/78705)
In r243317 I accidenta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
--- Comment #5 from David Malcolm ---
i386.md's define_expand "memory_blockage" has:
operands[0] = gen_rtx_MEM (BLKmode, gen_rtx_SCRATCH (Pmode));
so it's due to the difference in Pmode between i386 and x86_64.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
--- Comment #3 from David Malcolm ---
Sorry about the breakage.
Expected:
(cinsn 1 (set (mem/v:BLK (0|scratch:DI) [0 A8])
(unspec:BLK [
(mem/v:BLK (reuse_rtx 0) [0 A8])
] UNSPEC_MEMORY_BLOCKAGE)))
Actual:
(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
--- Comment #2 from kargl at gcc dot gnu.org ---
svn merge -r 243317:243316 .
fixes the problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78705
--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #0)
> gmake[3]: Entering directory '/mnt/kargl/obj/gcc'
> /mnt/kargl/obj/./gcc/xgcc -B/mnt/kargl/obj/./gcc/ -nostdinc -x c /dev/null
> -S -fself-test -o /dev/null
> /
