Lines Matching refs:preprocessor

73 The GNU C preprocessor is
75 a stand-alone preprocessor, and a preprocessor integrated with the C
83 preprocessor in previous versions of GCC would operate on text strings
206 @code{parsing_args} is nonzero when the preprocessor is collecting the
229 in the preprocessor; there are plenty of tests in the testsuite for
324 When the preprocessor was changed to return pointers to tokens, one
327 preprocessor, the future direction of the C family front ends, and even
330 Occasionally the preprocessor wants to be able to peek ahead in the
337 preprocessor wants to be able to test the current token with the
346 preprocessor lex all tokens on a line consecutively into a token buffer,
387 quite natural for the preprocessor, and as a result the only time cpplib
474 optimize the preprocessor's expansion algorithm wrong in quite subtle
487 The preprocessor stores macro expansions in tokenized form.  This
493 If the macro is a function-like macro the preprocessor also stores its
506 The preprocessor maintains a @dfn{context stack}, implemented as a
644 preprocessor: there needs to be a guarantee that re-reading its preprocessed
662 still try to abuse the preprocessor for things like Fortran source and
673 Look at how the preprocessor gets whitespace output correct
677 than a new line.  The stand-alone preprocessor can use this flag to
701 above, the preprocessor inserts a special token, which I call a
703 the subsequent token is special.  The preprocessor inserts padding
764 preprocessor is fixing up spacing because of padding tokens, and it
824 The stand-alone preprocessor faces a similar problem when determining
845 The preprocessor maintains a monotonic increasing line count, which is
882 preprocessor notices such header files, so that if the header file
933 that the preprocessor has not yet encountered anything that would