From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: thutt <thutt@vmware.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Narrowing down preprocessor-related potential defect
Date: Tue, 21 Jun 2022 20:35:07 +0100 [thread overview]
Message-ID: <CAH6eHdTPPVQ3QrxSDfcU_L9emsUkeMVLUFYDO49hmPV=cnDYYw@mail.gmail.com> (raw)
In-Reply-To: <25266.7279.168888.944211@thutt-l01.ddns.vmware.com>
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?
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.
next prev parent reply other threads:[~2022-06-21 19:35 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 [this message]
2022-06-21 19:47 ` Jonathan Wakely
2022-06-21 20:25 ` thutt
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='CAH6eHdTPPVQ3QrxSDfcU_L9emsUkeMVLUFYDO49hmPV=cnDYYw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=thutt@vmware.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).