This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 0/6] Convert gimple to a C++ class hierarchy
- From: Basile Starynkevitch <basile at starynkevitch dot net>
- To: gcc at gcc dot gnu dot org
- Cc: Diego Novillo <dnovillo at google dot com>, Jakub Jelinek <jakub at redhat dot com>, Michael Matz <matz at suse dot de>, Gabriel Dos Reis <gdr at integrable-solutions dot net>, David Malcolm <dmalcolm at redhat dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 31 Aug 2013 15:34:04 +0200
- Subject: Re: [PATCH 0/6] Convert gimple to a C++ class hierarchy
- Authentication-results: sourceware.org; auth=none
- References: <1377793216-22549-1-git-send-email-dmalcolm at redhat dot com> <alpine dot LNX dot 2 dot 00 dot 1308301532490 dot 9949 at wotan dot suse dot de> <CAAiZkiB-Z7GfDGNuWys+d6JW+ynbtfC_Yc5YHfN9M-to5uABXg at mail dot gmail dot com> <20130830140253 dot GO21876 at tucnak dot zalov dot cz> <CAAiZkiB=iJ7dwFEe7OKhMBXccMsu6950fE6Cy=h-a6JF0h=FTA at mail dot gmail dot com> <alpine dot LNX dot 2 dot 00 dot 1308301712450 dot 9949 at wotan dot suse dot de> <CAD_=9DRK4htu8jefZehb0Q4JDCozbCA2pr0Sq6rhX4JcW7QEDw at mail dot gmail dot com> <20130830153727 dot GQ21876 at tucnak dot zalov dot cz> <CAD_=9DRki+6uidqeKJ_=hU0u=hc6s-55XUDqr-qyhAp-kvxGjw at mail dot gmail dot com> <c5c7a870-69f0-4d04-91cd-f1a5e860f789 at email dot android dot com>
On Sat, 2013-08-31 at 11:57 +0200, Richard Biener wrote:
> Diego Novillo <dnovillo@google.com> wrote:
> >
> >Yes. Lawrence and I thought about moving gengtype inside g++. That
> >seemed like a promising approach.
>
>
> What do you do during stage1? Have a collector that never collects?
We could imagine that the successor of gengtype would be some GCC plugin
(which would generate C++ code for marking and GC and PCH purposes,
perhaps using ad-hoc attributes and pragmas)
Then for bootstrapping purposes, we could put the generated C++ code in
the source repository (like we already do for configure, or
fixincludes/fixincl.x etc...). Hence stage1 would be buildable with the
generated C++ code in the repository.
A more difficult issue is that the set of GTY-ed types is target
specific and depends upon the .../configure argument at build time.
Perhaps we could consider processing all of it (i.e. every GTY-ed class
declaration), and have our gengtype successor plugin emit appropriate
#if in the generated C++ code.
Of course having gengtype replaced by a plugin requires such a plugin to
be developed and GCC maintainers to have access to some gcc...
Cheers
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***