From: thutt@vmware.com
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: thutt <thutt@vmware.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Narrowing down preprocessor-related potential defect
Date: Tue, 21 Jun 2022 13:25:53 -0700 [thread overview]
Message-ID: <25266.10577.30790.163038@thutt-l01.ddns.vmware.com> (raw)
In-Reply-To: <CAH6eHdTPPVQ3QrxSDfcU_L9emsUkeMVLUFYDO49hmPV=cnDYYw@mail.gmail.com>
Jonathan Wakely writes:
> âs External Email
>
> On Tue, 21 Jun 2022 at 20:31, thutt--- via Gcc <gcc@gcc.gnu.org> 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?
I am not using a standalone preprocessor. Only using gcc directly to
preprocess and compile the file results in the failure.
> The usual approach is to add -save-temps to the gcc invocation, so it
> leaves the preprocessed output in a separate .i file.
This doesn't have a satisfactory outcome. The file is preprocessed
and multiple spaces appear to be replaced with a single space. The
resultant output has no tabs that are not in quoted strings. It is
currently believed the failure is produced when a mix of tabs and
spaces are present.
>
> N.B. it's a warning, not an error. You told GCC to turn that warning
> into an error.
I'm aware of that. We treat all warnings as errors.
--
prev parent reply other threads:[~2022-06-21 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 19:30 thutt
2022-06-21 19:35 ` Jonathan Wakely
2022-06-21 19:47 ` Jonathan Wakely
2022-06-21 20:25 ` thutt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25266.10577.30790.163038@thutt-l01.ddns.vmware.com \
--to=thutt@vmware.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).