Re: [PATCH], PR target/93932, GCC 9 backport, Do not use input_operand for variable vector extract insns on PowerPC

2020-02-28 Thread Segher Boessenkool
On Thu, Feb 27, 2020 at 06:53:10PM -0500, Michael Meissner wrote: > On Thu, Feb 27, 2020 at 04:57:28PM -0600, Segher Boessenkool wrote: > > On Thu, Feb 27, 2020 at 03:38:54PM -0500, Michael Meissner wrote: > > > Here are the equivalent changes for PR target/93932 for the GCC 9 branch. > > > I >

Re: [PATCH], PR target/93932, GCC 9 backport, Do not use input_operand for variable vector extract insns on PowerPC

2020-02-27 Thread Michael Meissner
On Thu, Feb 27, 2020 at 04:57:28PM -0600, Segher Boessenkool wrote: > Hi, > > On Thu, Feb 27, 2020 at 03:38:54PM -0500, Michael Meissner wrote: > > Here are the equivalent changes for PR target/93932 for the GCC 9 branch. I > > have built both big and little endian PowerPC linux compilers and

Re: [PATCH], PR target/93932, GCC 9 backport, Do not use input_operand for variable vector extract insns on PowerPC

2020-02-27 Thread Segher Boessenkool
Hi, On Thu, Feb 27, 2020 at 03:38:54PM -0500, Michael Meissner wrote: > Here are the equivalent changes for PR target/93932 for the GCC 9 branch. I > have built both big and little endian PowerPC linux compilers and both > bootstrapped. The make check actually fixes the tests that were broken

[PATCH], PR target/93932, GCC 9 backport, Do not use input_operand for variable vector extract insns on PowerPC

2020-02-27 Thread Michael Meissner
Here are the equivalent changes for PR target/93932 for the GCC 9 branch. I have built both big and little endian PowerPC linux compilers and both bootstrapped. The make check actually fixes the tests that were broken by the register allocation behavior. Can I check these patches into GCC 9?