This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] avoiding too narrow register classes in reload
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: bernds_cb1 at t-online dot de (Bernd Schmidt)
- Cc: gcc at gcc dot gnu dot org
- Date: 14 Dec 2004 18:52:56 -0200
- Subject: Re: [RFC] avoiding too narrow register classes in reload
- Organization: Red Hat Global Engineering Services Compiler Team
- References: <oracshki96.fsf@livre.redhat.lsd.ic.unicamp.br><41BF1302.7080700@t-online.de>
On Dec 14, 2004, bernds_cb1@t-online.de (Bernd Schmidt) wrote:
>> This is what causes the problem I'm running into: if this alternative
>> is selected (and it will often be), we end up forced to use one of the
>> first two argument registers for the reload, and this will fail if the
>> reload is needed in the middle of a function call sequence.
> What does the insn that it's trying to reload look like?
(set (mem addr) (pseudo))
addr is a legitimate address, that doesn't require any reloads.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}