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
207 @code{parsing_args} is nonzero when the preprocessor is collecting the
230 in the preprocessor; there are plenty of tests in the testsuite for
325 When the preprocessor was changed to return pointers to tokens, one
328 preprocessor, the future direction of the C family front ends, and even
331 Occasionally the preprocessor wants to be able to peek ahead in the
338 preprocessor wants to be able to test the current token with the
347 preprocessor lex all tokens on a line consecutively into a token buffer,
388 quite natural for the preprocessor, and as a result the only time cpplib
475 optimize the preprocessor's expansion algorithm wrong in quite subtle
488 The preprocessor stores macro expansions in tokenized form.  This
494 If the macro is a function-like macro the preprocessor also stores its
507 The preprocessor maintains a @dfn{context stack}, implemented as a
645 preprocessor: there needs to be a guarantee that re-reading its preprocessed
663 still try to abuse the preprocessor for things like Fortran source and
674 Look at how the preprocessor gets whitespace output correct
678 than a new line.  The stand-alone preprocessor can use this flag to
702 above, the preprocessor inserts a special token, which I call a
704 the subsequent token is special.  The preprocessor inserts padding
765 preprocessor is fixing up spacing because of padding tokens, and it
825 The stand-alone preprocessor faces a similar problem when determining
846 The preprocessor maintains a monotonic increasing line count, which is
883 preprocessor notices such header files, so that if the header file
934 that the preprocessor has not yet encountered anything that would