Alan Modra - Re: LEGITIMIZE_RELOAD_ADDRESS vs address_reloaded (original) (raw)
This is the mail archive of the gcc@gcc.gnu.orgmailing 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] |
- From: Alan Modra
- To: Ulrich Weigand
- Cc: gcc at gcc dot gnu dot org, David Edelsohn
- Date: Mon, 28 Nov 2005 09:58:56 +1030
- Subject: Re: LEGITIMIZE_RELOAD_ADDRESS vs address_reloaded
- References: <20051125040915.GM19599@bubble.grove.modra.org> <200511251820.jAPIKqJ7016569@53v30g15.boeblingen.de.ibm.com>
On Fri, Nov 25, 2005 at 07:20:52PM +0100, Ulrich Weigand wrote:
c) Modify the ppc 'Z' constraint to match the indexed address reload generates. This would rely on the pattern we generate in LEGITIMIZE_RELOAD_ADDRESS never being generated elsewhere. [snip]
Overall, I'd tend to prefer something along the lines of (c), in particular as it would also catch the cases where LEGITIMIZE_RELOAD_ADDRESS isn't actually involved, as you note:
Thanks. I went ahead and implemented this, and yes, the testcase in pr24997 has better code in other places too.
-- Alan Modra IBM OzLabs - Linux Technology Centre
- References:
- LEGITIMIZE_RELOAD_ADDRESS vs address_reloaded
* From: Alan Modra - Re: LEGITIMIZE_RELOAD_ADDRESS vs address_reloaded
* From: Ulrich Weigand
- LEGITIMIZE_RELOAD_ADDRESS vs address_reloaded
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |