This is the mail archive of the
mailing list for the GCC project.
Re: Tags out of gcc
- From: Adrian May <adrian dot alexander dot may at gmail dot com>
- To: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, gcc Mailing List <gcc at gcc dot gnu dot org>
- Date: Sun, 5 Oct 2014 09:39:59 +0800
- Subject: Re: Tags out of gcc
- Authentication-results: sourceware.org; auth=none
- References: <CAESRpQC1xRZuFGyzEPvJACq8+139HVM2+H5J7VgZVsZy=A0muQ at mail dot gmail dot com> <CAH6eHdSjcBnsS0CD7QfHZpYaCkE8MuhyM1DM=_GLM_8i5h5FTg at mail dot gmail dot com> <CAESRpQDwwqzh6cmvXueZOyZGbuACMSCRNAp8MF0OsGVK1=QJOQ at mail dot gmail dot com>
At first sight, I prefer the hooks approach. Not just cos I'm a noob
(although that is a compelling reason in itself) but also because it
happens during the main compile. A separate innovation could have
different flags so it wouldn't be authoritative anymore.
But it absolutely has to follow the preprocessor, so how do I do that?
I'm a bit surprised about that being a problem cos when I look at
preprocessor output it looks very convenient - I get one big file but
it's full of clues as to where it all came from. Perhaps I have to
hook those clues.