This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: reload displacement optimization
- To: Richard Henderson <rth at cygnus dot com>
- Subject: Re: reload displacement optimization
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sun, 05 Apr 1998 12:35:12 -0600
- cc: Jim Wilson <wilson at cygnus dot com>, Joern Rennecke <amylaar at cygnus dot co dot uk>, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <19980404183803.07177@dot.cygnus.com>you write:
> On Thu, Apr 02, 1998 at 11:50:05PM -0700, Jeffrey A Law wrote:
> > Note the documentation says nothing about the need to call push_reload
> > on the address you actually want reloaded.
>
> The documentation said that "you may" call push_reload to get things
> done. I've bumped push_reload up to the top of the list to make it
> more obvious, and strengthened the wording to "should".
>
> > I also vaguely remember a question about any structure sharing
> > assumptions made by LEGITIMIZE_RELOAD_ADDRESS. Do you need to
> > call copy_rtx on the address?
>
> The matter of structure shareing is discussed quite clearly, I think,
> immediately after where it discusses push_reload. Copy_rtx is mentioned
> two paragraphs below as something that you might want to use.
I must have missed both of them. Of course that's what I get for
reading the *&(@#$ texi source directly. :-)
jeff