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: [RFC] avoiding too narrow register classes in reload

From: bernds_cb1 at t-online dot de (Bernd Schmidt)
To: Alexandre Oliva <aoliva at redhat dot com>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 14 Dec 2004 17:21:22 +0100
Subject: Re: [RFC] avoiding too narrow register classes in reload
References: <oracshki96.fsf@livre.redhat.lsd.ic.unicamp.br>

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?

Bernd

Follow-Ups:
- Re: [RFC] avoiding too narrow register classes in reload
  - From: Alexandre Oliva

References:
- [RFC] avoiding too narrow register classes in reload
  - From: Alexandre Oliva

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