[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 Michael Matz changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #28 from Segher Boessenkool --- Author: segher Date: Wed Nov 23 14:33:13 2016 New Revision: 242757 URL: https://gcc.gnu.org/viewcvs?rev=242757=gcc=rev Log: combine: Convert subreg-of-lshiftrt to zero_extract properly (PR78390)

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 Richard Biener changed: What|Removed |Added Priority|P3 |P1

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 Richard Biener changed: What|Removed |Added CC||doko at gcc dot gnu.org --- Comment

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #26 from Andreas Schwab --- Note that the patch in comment 8 is already included in r242526.

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #25 from Dominik Vogt --- A quick regression test with both patches; s390x with just -m64 and -languages=c has only two failures left: +FAIL: gcc.target/s390/risbg-ll-1.c scan-assembler f43:\\n\\trisbg\\t%r2,%r2,32,128+61,64-12

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #24 from Andreas Schwab --- This also fixes bootstrap on ia64.

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #23 from Michael Matz --- (In reply to Dominik Vogt from comment #22) > Does this patch replace the one in comment 8 or should they both be used? I checked it in isolation, but the former one does fix a bug as well, so probably use

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #22 from Dominik Vogt --- Does this patch replace the one in comment 8 or should they both be used?

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #21 from Dominik Vogt --- (In reply to Michael Matz from comment #16) > Uhh: > > Successfully matched this instruction: > (set (subreg:DI (reg:SI 73) 0) > -(lshiftrt:DI (reg/v:DI 63 [ X ]) > -(const_int 56 [0x38]))) >

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #20 from Michael Matz --- The below patch fixes at least the gcc.c-torture/execute/20030408-1.c testcase. Checking others as well, perhaps I manage to bootstrap later. But if Dominik is faster... :) diff --git a/gcc/combine.c

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #19 from Dominik Vogt --- (In reply to Segher Boessenkool from comment #17) > Combine should probably not try to generate this extract, I wonder if it > can exist on any target. So where is it coming from? > > Of course the target

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #18 from Michael Matz --- (In reply to Segher Boessenkool from comment #17) > Combine should probably not try to generate this extract, I wonder if it > can exist on any target. So where is it coming from? Easy: (subreg:SI

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #17 from Segher Boessenkool --- Combine should probably not try to generate this extract, I wonder if it can exist on any target. So where is it coming from? Of course the target should not "successfully" match it ;-)

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #16 from Michael Matz --- Uhh: Successfully matched this instruction: (set (subreg:DI (reg:SI 73) 0) -(lshiftrt:DI (reg/v:DI 63 [ X ]) -(const_int 56 [0x38]))) +(zero_extract:DI (reg/v:DI 63 [ X ]) +

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #15 from Michael Matz --- (In reply to Dominik Vogt from comment #14) > With the fix I couldn't reproduce the error message in four attempts, but > genattrtab still hangs. Maybe this is bad luck, but maybe the error is > gone.

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #14 from Dominik Vogt --- With the fix I couldn't reproduce the error message in four attempts, but genattrtab still hangs. Maybe this is bad luck, but maybe the error is gone. Running a regression test without bootstrapping on

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #13 from Dominik Vogt --- I'm doing this on s390x right now. Just takes some more time.

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #12 from Michael Matz --- (In reply to Andreas Schwab from comment #11) > That didn't fix the ia64 bootstrap failure. Would have been too easy I guess :-) Okay, can you try to find a testcase that regressed by not bootstrapping but

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #11 from Andreas Schwab --- That didn't fix the ia64 bootstrap failure.

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #10 from Michael Matz --- (In reply to Dominik Vogt from comment #9) > On Thu, Nov 17, 2016 at 03:03:03PM +, matz at gcc dot gnu.org wrote: > > I'm just bootstrapping s390x with the fix; would you like me to > run a regression

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #9 from Dominik Vogt --- On Thu, Nov 17, 2016 at 03:03:03PM +, matz at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 > > --- Comment #8 from Michael Matz --- > The aarch64 fail is fixed by the

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #8 from Michael Matz --- The aarch64 fail is fixed by the below patch. It will take a while for me to try this on s390, so if somebody beats me to test this I won't complain. diff --git a/gcc/combine.c b/gcc/combine.c index

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 Michael Matz changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 Andreas Schwab changed: What|Removed |Added Target|s390x |s390x-*-*,

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #5 from Dominik Vogt --- (In reply to Andreas Schwab from comment #3) > Does it help to revert r242414? Yep. r242414 has introduced the problem. (Happens only with --with-arch=zEC12.)

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #4 from Dominik Vogt --- There's another error that our dailybuild system found yesterday. May have the same cause. build/genmatch --gimple /home/dailybuild/gnu-dailybuild/arena/20161116/gcc-head/src/gcc/match.pd \ >

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #3 from Andreas Schwab --- Does it help to revert r242414?

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 --- Comment #2 from Dominik Vogt --- Both, the hang in genattrtab and the error message happen in stage 2.

[Bug bootstrap/78390] [7 Regression] Bootstrap failure: match.pd: cannot determine type of operand

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78390 Richard Biener changed: What|Removed |Added Keywords||build, wrong-code