This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] Move C front end to its own directory (1/3)
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Steven Bosscher <stevenb dot gcc at gmail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, mark at codesourcery dot com
- Date: Sat, 5 Jun 2010 10:26:52 +0000 (UTC)
- Subject: Re: [patch] Move C front end to its own directory (1/3)
- References: <AANLkTikdj4_E-Bm_Ib971thjOAgUztsRXfUuolXbLHli@mail.gmail.com>
On Sat, 29 May 2010, Steven Bosscher wrote:
> Most of this is trivial updating of paths. The only complication is
> that gengtype does not understand that files can come from
> subdirectories that are not front-end specific, so I needed a rather
Neither does po/exgettext, which looks for directories with config-lang.in
plus the config/ directory and its immediate subdirectories. So that
script will need to know about c-family as well. (This limitation could
be turned into a feature: if target-side files moved to the toplevel
libgcc directory, generator files to a subdirectory of gcc/ and targets
using mips-tdump or mips-tfile were deprecated, then po/EXCLUDES would no
longer be needed.)
I have not yet otherwise reviewed the patch.
--
Joseph S. Myers
joseph@codesourcery.com