This is the mail archive of the gcc@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] |
Neil Booth <neil@daikokuya.co.uk> writes:Then we'll first have to un-tangle some middle-end/front-end dependencies (such as STATEMENT_CODE_P and other tree-inliner things, various flags, etc.) or it will still be messy.
Following a brief discussion with rth at the summit, and just now on IRC, I thought I'd post what the current plan is.
1) Create a directory fe/ 2) Create a directory fe/c/ 3) Move c-specific and C common files, like c-lex.c, there. 4) Move objc/ to fe/ too.
I originally suggested fe/c/c/ fe/c/cp/ and fe/c/objc, but Zack thought that was overkill and made configury harder, though I still like the separation myself.
cp/, f/ and java/ and (ugh) ada/ should be moved too, but I'm not
volounteering to do those.
Separating the files so that we have for each "module" or logical unit a separate directory, sounds fine!
Will this also result in a backend directory?
Gr. Steven
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |