This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] Design issues with multiple IRs
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- To: Diego Novillo <dnovillo at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 6 Dec 2001 20:40:56 +0000
- Subject: Re: [RFC] Design issues with multiple IRs
- References: <20011206143203.B8021@tornado.cygnus.com>
Diego Novillo wrote:-
> But that doesn't fix the problem of what to do with common code.
> We will likely have a lot of tree code that can be shared among
> the different front-ends. Maybe we should start putting common
> code in tree-* and have C-specific files in c-tree-*?
When we create a c/ directory, I'd put C-specific stuff in there. I
think the plan was to wait for 6 to 12 months to see if e.g.
subversion gets to a stable useable point, and maybe move to that
since it can move files properly.
> Now, what happens when we start introducing trees that are
> language independent? Should we have another set of directories
> for each IR? I haven't thought this through, but initially I can
> picture something like this:
>
> gcc
> |
> +-> fe
> | +-> c
> | +-> cpp
> | +-> java
> | ...
> |
> +-> ir +-> tree (these would be language independent trees)
> | +-> RTL
> |
> +-> config +-> ...
I'd rather not have the ir directory; /tree and /rtl would be great.
Just MO.
Neil.