Narrowing down preprocessor-related potential defect

Jonathan Wakely
Tue Jun 21 19:47:49 GMT 2022

On Tue, 21 Jun 2022, 20:35 Jonathan Wakely, <> wrote:

> On Tue, 21 Jun 2022 at 20:31, thutt--- via Gcc <> wrote:
> >    I am here to solicit ideas on how to further narrow this this
> >    down.  Is there any undocumented option that I can use to cause the
> >    standalone preprocessor to produce output identical to input?
> >    Note that '-traditional-cpp' does not work because some of the code
> >    is not recognized (variadic macros, for example).
> This seems off-topic for the gcc mailing list. It belongs on the gcc-help
> list.
> Have you tried not using a standalone preprocessor?
> The usual approach is to add -save-temps to the gcc invocation, so it
> leaves the preprocessed output in a separate .i file.
> N.B. it's a warning, not an error. You told GCC to turn that warning
> into an error.

GCC has a whole guide to test case reduction here:

I don't know how much will be applicable it usable in this instance.

More information about the Gcc mailing list