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: Ian Lance Taylor <ian at wasabisystems dot com>
- To: "Zack Weinberg" <zack at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 18 Feb 2004 23:50:06 -0500
- Subject: Re: Why is targetm.fixed_condition_code_regs a function?
- References: <87wu6kc72s.fsf@egil.codesourcery.com>
"Zack Weinberg" <zack@codesourcery.com> writes:
> While looking to see what had fixed the redundant compare instruction
> generation for i386 I noticed this new target hook. I don't see why
> it should be a function. A two-element array of unsigned int should
> suffice - if both are INVALID_REGNUM, then the target doesn't use this
> kind of comparison, else one or both are hard register numbers. I
> don't think it is possible for this to change at runtime...
Sure, it could be an array. The information is only retrieved once
per function being compiled, so I doubt it will make much difference
performance-wise. I can change it if people think it would be
clearer.
Ian