This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: LRA reload produces invalid insn

From: Peter Bergner <bergner at linux dot ibm dot com>
To: Vladimir Makarov <vmakarov at redhat dot com>, Paul Koning <paulkoning at comcast dot net>
Cc: GCC Development <gcc at gcc dot gnu dot org>
Date: Fri, 2 Nov 2018 08:34:07 -0500
Subject: Re: LRA reload produces invalid insn
References: <E7E288AE-C84B-4722-8153-29F072636300@comcast.net> <cd72f1ce-7e2c-5d75-ae45-972d4aa5e3fb@redhat.com>

On 11/1/18 10:37 PM, Vladimir Makarov wrote:
> On 11/01/2018 08:25 PM, Paul Koning wrote:
>> Is this an LRA bug, or is there something I need to do in the target to prevent this happening?
> It is hard to say whose code is responsible for this.  It might be a wrong machine-dependent code or a LRA bug.
> 
> Paul, could you send me full LRA dump file (.reload).  It might help me to say more specific reason for the bug.  LRA has iterated sub-passes and the full dump can say where LRA started to behave wrongly.
> 

I'll note that when we ported the rs6000 (ie, ppc*) port over to LRA
from reload, we hit many target problems.  It seems LRA is much less
forgiving to bad constraints, predicates, etc. than reload was.
I think that's actually a good thing.

Peter

Follow-Ups:
- Re: LRA reload produces invalid insn
  - From: Paul Koning

References:
- LRA reload produces invalid insn
  - From: Paul Koning
- Re: LRA reload produces invalid insn
  - From: Vladimir Makarov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]