This is the mail archive of the gcc-patches@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] |
That's orthogonal. There's no reason you can't write a great front end using trees.
But it is hard to write a great back end using trees when at least one front end has its own set of rules about using trees.
G++ abuses trees in horrible ways by linking together trees of different kinds (e.g. TREE_LISTs, *_DECLs, and OVERLOADs) and also by overloading many tree fields (e.g. TREE_TYPE). This makes cleaning up some fields in the existing tree structures a tough job.
G++ also needs to define a lot of language-specific tree nodes because
it wants a representation that is close to the source code.
-- Mark Mitchell CodeSourcery, LLC mark@codesourcery.com (916) 791-8304
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |