> On Nov 1, 2018, at 8:49 PM, Peter Bergner <berg...@linux.ibm.com> wrote:
>
> On 11/1/18 7:25 PM, Paul Koning wrote:
>> I'm running the testsuite on the pdp11 target, and I get a failure when
>> using LRA that works correctly with the old allocator. The issue is that
>> LRA is producing an insn that is invalid (it violates the constraints stated
>> in the insn definition).
> [snip]
>> which is the correct sequence given the matching operand constraint in the
>> define_insn.
>>
>> Is this an LRA bug, or is there something I need to do in the target to
>> prevent this happening?
>
> What do you mean by "old allocator"? Just an older revision? Does it work
> before my
> revision 264897 commit and broken after? If so, could you try the following
> to see
> whether that fixes things for you?
>
> https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01757.html
>
> My commit above exposed some latent LRA bugs and my patch above tries
> to fix issues similar to what you're seeing.
>
> Peter
That doesn't cure this particular problem; the ICE is still there with the same
error message (identical failing insn) as before.
paul
