[GCC-XML] tarball

Roman Yakovenko roman.yakovenko at gmail.com
Thu Oct 2 08:12:34 EDT 2008


On Wed, Oct 1, 2008 at 6:08 PM, Brad King <brad.king at kitware.com> wrote:
> Sagrailo wrote:
>> Related question: is there a chance to have gccxml merged into the gcc
>> source tree (as some kind of back-end, I guess) at some point?
>
> There are two parts to gccxml.
>
> 1.) The patched GCC parser to perform the dump
> 2.) The front-end which simulates native compilers
>
> I cannot say for sure that #1 will never be in gcc upstream,

Did you you see the following discussion:
http://gcc.gnu.org/ml/gcc/2008-09/msg00292.html

May be "never" can be transform to something else :-)

> but #2 will
> not.  The #2 part has a whole bunch of compatibility patches for system
> headers of native compilers from many different vendors.  It allows the
> GCC compiler to read the system header files from these other compilers.
>  This is needed so that the dumped interface exactly matches what the
> user's compiler would see.

Are there some changes to the GCC itself, or this is just a set of
patched header files?

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/


More information about the gccxml mailing list