This is the mail archive of the gcc-help@gcc.gnu.org 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 : Re : Generation of GENERIC tree


but gcc manual 2008, gcc internals 2008, many articles and figures in GCC summit 2006, 2007 and 2008 talk about GENERIC ?
did C front end call the function c_genericize or not ?

thank you

Asma




----- Message d'origine ----
De : Andrew Haley <aph@redhat.com>
À : charfi asma <charfiasma@yahoo.fr>
Cc : Ian Lance Taylor <iant@google.com>; gcc-help@gcc.gnu.org
Envoyé le : Mercredi, 24 Juin 2009, 11h56mn 33s
Objet : Re: Re : Generation of GENERIC tree

charfi asma wrote:
>    

> I am interested too in the GENERIC
> tree
> I compile hello.cpp using g++
> -fdump-tree-all, I do not get a generic intermediate representation,
> there was (.tu, .class, .original, .gimple, .vcg ...)
> To look at the GENERIC tree, I
> compile hello.java using gcj (as mentioned in the answer bellow: "I
> recommend looking at any gcc frontend other than the C/C++ frontends
> to see how it is done....")
> But when I compile java file using
> the same option (fdump-tree-all) I do not get .generic as I expect..
> Before .gimple, gcj generate only .original

That's right.  gcj transforms its front-end trees straight into GIMPLE.  I
can't see any purpose to going via GENERIC.

Andrew.





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