This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why is targetm.fixed_condition_code_regs a function?
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, Ian Lance Taylor <ian at wasabisystems dot com>
- Date: Wed, 18 Feb 2004 18:44:08 -0800
- Subject: Re: Why is targetm.fixed_condition_code_regs a function?
- References: <87wu6kc72s.fsf@egil.codesourcery.com><20040219014524.GA23745@redhat.com>
Richard Henderson <rth@redhat.com> writes:
> On Wed, Feb 18, 2004 at 03:15:55PM -0800, Zack Weinberg wrote:
>> I don't think it is possible for this to change at runtime...
>
> I thought maybe it might change based on -march switches,
> particularly the presence or absence of the second register.
Hmm, I suppose, but couldn't we deal with that by modifying the value
in the array in override_options? Targets already do plenty of
diddling of the targetm structure at that point.
zw