This is the mail archive of the 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: GCC 5? (was Re: GCC 4.7.0RC: Mangled names in cc1)


Richard Guenther <> skribis:

> But no, I'm not volunteering (I'm volunteering to do the review work).
> The above has the same issue as the "we-want-to-be-more-like-LLVM"
> stuff - it lacks the people to actually implement it, and GCC at its
> present state still has to evolve, we can't and do not want to just spend
> a complete release or two with just turning GCC upside-down.

What David proposes looks great, but also fairly intrusive and

Perhaps a more incremental approach could be taken.  For instance, I
would argue that changes to the tree and GIMPLE APIs could be made
conservatively, on the grounds that they are most likely used by
plug-ins out there.  IOW, rather than a commitment to a stable API,
which would hinder the work of GCC developers, this would be an informal
agreement to not make the plug-in developers life too hard.

In the example of name mangling, Iâd just have wrapped in âextern "C"â
all the headers listed in âPLUGIN_HEADERSâ in gcc/  The
rationale is that it simplifies plug-in maintenance, while not impeding
development work in 4.7.

In the longer term, providing a GCC plug-in alongside oneâs library or
program should become as natural as providing a syntax highlighting mode.


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