> On Mon, Jun 2, 2008 at 20:37, Kenneth Zadeck <[EMAIL PROTECTED]> wrote: > > > the problem with making this a langhook is that there is no "there-there" in > > that on the serialize in side, you would have to recreate the c++ front end > > code that expects this tree code. (if there is no such code, then this tree > > code could/should have been removed before you got there. On the other > > hand, if this tree code needs to be there, then copying the c++ front end > > code that processes it later is a bad road to go down. > > Yes, you are right. In this case, the code sneaks in through a > RECORD_TYPE which contains the TEMPLATE_DECL in its maxval field, > because that's where C++ stores TYPE_METHODS. > > I don't really see any need for us to handle TEMPLATE_DECL outside of > the C++ FE, so I'm tempted to just totally ignore language codes when > we see them in output_tree(). I will go with this for now. On the > way in, we simply ignore the field.
Sure if it works, we should be lowering the types during gimplification so we don't need to store all this in memory... But C++ FE still use its local data later in stuff like thunks, but we will need to cgraphize them anyway. Honza > > > Diego.
