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: Can we speed up the gcc_target structure?


"Zack Weinberg" <zack@codesourcery.com> writes:

> Of course inefficiencies are going to be introduced if we just convert
> each macro to a target hook with the same semantics.  But that isn't
> the only option on the table.  The right thing is to redesign this
> interface so that it doesn't *need* 100+ macros and toggles.  If this
> is done properly, then not only should there be no inefficiency
> introduced by going through the target vector, but also we would have
> something that was straightforward to maintain and straightforward to
> add support for new architectures.

I agree with this paragraph.  Our function-call ABI description is
very suboptimal, and performance is the least of the problems; I think
there are still targets where no-one can describe the ABI without
making reference to function.c.

-- 
- Geoffrey Keating <geoffk@geoffk.org>


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