cpplib startup patch
Mon Jul 12 13:52:00 GMT 1999
Zack Weinberg wrote:
> Dave said something about cccp doing the same thing - that's not a bug for
> cccp because one normally does not run preprocessed text through cccp again.
> It's only because there's no way to turn the preprocessor _off_ in a
> USE_CPPLIB front end that you see this bug. (And that is the real bug.)
The gcc driver seems to be smart enough to not call the front end if the file is of
type .i or .ii and preprocessed output is being generated. When actually compiling
a .i or .ii, output_line_command has no effect because CPP_OPTIONS
(pfile)->no_output is set. So what's the bug? Maybe I need an example (i.e.
testcase, compile options and erroneous output). Or maybe I just need a new brain.
More information about the Gcc-patches