This is the mail archive of the gcc-patches@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: [patch] Split c_register_addr_space in separate functions for C and C++ front ends


On Sat, May 29, 2010 at 12:37 AM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
>
> I'd be happy to move the call site anywhere else you suggest. ?But I'm
> wondering what you mean by "C target hook". ?The struct targetcm, which
> I'd been thinking of using, seems itself to contain "C-family" target
> hooks, and not "C-only" target hooks, right?

I plan to introduce target-$lang.h.  If the front ends are to be
separate modules, you can't have it link to all target hooks.  I am
not sure yet what to do with the common hooks.  Most "C-only" hooks
are common to all C-family languages. The SPU trick is unusual...
Maybe needs a new targetcm.register_target_keyword or something. Not
sure yet, but if/when I get to the point where it matters, I'll
probably come back to you for some help :-)

Ciao!
Steven


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