Re: Narrowing down preprocessor-related potential defect

2022-06-21 Thread thutt--- via Gcc
Jonathan Wakely writes: > âs  External Email > > 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 out

Re: Narrowing down preprocessor-related potential defect

2022-06-21 Thread Jonathan Wakely via Gcc
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 out

Re: Narrowing down preprocessor-related potential defect

2022-06-21 Thread Jonathan Wakely via Gcc
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' doe

Narrowing down preprocessor-related potential defect

2022-06-21 Thread thutt--- via Gcc
Hello folks, I am not subscribed to this mailing list, so please address responses directly to me. I have a program that generates this error: .c: In function ‘f0’: .c:117:4: error: this ‘else’ clause does not guard... [-Werror=misleading-indentation] 117 | //#en