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: target macro->hook migration idea


DJ Delorie <dj@redhat.com> writes:

>> I like your plan.  I'd thought about doing something similar for a
>> long time, but I was always stuck on how to prevent half-migrations.
>> You've got a scheme for that.
>
> Well, a target could still be half-migrated, but it would still bear
> the "not migrated" stigma.
>
> We can work on the common-code migration over time; we should create
> the poison conditional stuff when we're pretty much done.

Sounds good.

I have one concern with this part, which is, there are a bunch of
macros that are used mostly - or even entirely - by other macros.
Things like ASM_OUTPUT_INT.  What do you think we should do with them?

> The first step is to design the target structure.  We can add hooks
> to the structure without using them, so we can start on this part
> "right away" without needing to schedule migration time yet.

And another concern with this part: I'm leery of trying to design
target hooks /a priori/.  Every time I've done target hook
conversions, the proper form has emerged organically from the morass.
I don't really have a better suggestion, though.

zw


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