Re: [PING] allow front-end/gcc interface files in lang subdir

[Arnaud Charlet <charlet at adacore dot com>]

> Ping for the gengtype part of the changes suggested in
> 
>   http://gcc.gnu.org/ml/gcc-patches/2008-05/msg00808.html
> 
> In addition to allowing improvements of front-end subtree
> origanizations, the patch clarifies a couple of gengtype's internal
> functions.
> 
> Ada wise, this is preparatory work for a real move of the build plus
> gigi files, which we have done internally and would really like to
> synchronize to further help our changes submission/integration process.

Indeed. To give a little bit more background, we've switched recently
to subversion for our AdaCore repository to handle GNAT sources, which makes
it much easier to submit our changes to the FSF tree.

As part of this switch, we needed to change the source structure to put
the files that interface with GCC (gigi + Makefiles) in a separate directory,
so that it is easy for us to use the same front-end sources with several
different back-ends (e.g. GCC 4.1, GCC 4.3, GCC 4.4, and other non GCC
back-ends as well, such as our JVM back-end and our .NET back-end) without
having to create and maintain separate branches for 95% of the sources.

With CVS, we used to have partial branches (with only a few files branches)
to achieve this effect (and use of e.g. cvs update -f), which has no
direct equivalent in subversion, hence the use of two directories, which
make sense anyway, since it's a nice separation between pure front-end
files, and files that makes the interface/brige between front-end files
(back-end agnostic) and GCC.

So being able to have the same directory structure in the FSF tree will allow
us to continue submitting our changes more efficiently.

Arno