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: Reload generating memory ref in memory ref

From: Jeff Law <law at redhat dot com>
To: Richard Henderson <rth at redhat dot com>
Cc: Michael Eager <eager at eagercon dot com>, Ian Lance Taylor <iant at google dot com>, GCC <gcc at gcc dot gnu dot org>
Date: Mon, 08 Dec 2008 17:50:29 -0700
Subject: Re: Reload generating memory ref in memory ref
References: <4938387E.3000105@eagercon.com> <m3bpvr2qqo.fsf@google.com> <493C2260.6090305@redhat.com> <493C2FDD.3080009@eagercon.com> <493D52F4.3010203@redhat.com>

Richard Henderson wrote:

Michael Eager wrote:

Another possibility is illegal rtl sharing.


If you mean that an rtx would be pointed to by two different
insn's, how would that happen?  (Excluding someone mucking
things up deliberately or accidentally.)


Generally this sort of mistake happens in the backend somewhere.
E.g. when it is fooling about with insn splitters (with C as
opposed to machine-generated via patterns).

A badly written LEGITIMIZE_RELOAD_ADDRESS can trigger this kind of failure as well.

jeff

Follow-Ups:
- Re: Reload generating memory ref in memory ref
  - From: Michael Eager

References:
- Reload generating memory ref in memory ref
  - From: Michael Eager
- Re: Reload generating memory ref in memory ref
  - From: Ian Lance Taylor
- Re: Reload generating memory ref in memory ref
  - From: Richard Henderson
- Re: Reload generating memory ref in memory ref
  - From: Michael Eager
- Re: Reload generating memory ref in memory ref
  - From: Richard Henderson

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