From: Richard Biener <richard.guenther@gmail.com>
To: Dave Blanchard <dave@killthe.net>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Change in preprocessor behavior
Date: Tue, 21 Jun 2022 09:28:00 +0200 [thread overview]
Message-ID: <CAFiYyc1M13dxBFok7wwtB6LPJZe68V9UojqWWS4_6B9iWp-XBA@mail.gmail.com> (raw)
In-Reply-To: <20220620193418.37581569f8a43bbaded229e6@killthe.net>
On Tue, Jun 21, 2022 at 2:34 AM Dave Blanchard <dave@killthe.net> wrote:
>
> At some point between GCC 9 and GCC 12, the preprocessor started behaving differently. Before if GCC were launched as /lib/cpp or /usr/bin/cpp (I think) it would assume the user wanted to preprocess something and automatically launch in preprocessor mode. Now the behavior has changed and it just acts as the normal compiler. Can someone kindly point me to the patch or commit where this feature was changed, and the rationale for doing so? Thank you.
It still does that for me.
> ~/install/gcc-12/usr/local/bin/cpp t.c
# 0 "t.c"
# 0 "<built-in>"
# 0 "<command-line>"
...
maybe you can be more specific as to how you invoke 'cpp'. Did you
build gcc yourself? What
is the 'cpp' you invoke (is it maybe a script or a symlink?)
Richard.
> --
> Dave Blanchard <dave@killthe.net>
next prev parent reply other threads:[~2022-06-21 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 0:34 Dave Blanchard
2022-06-21 7:28 ` Richard Biener [this message]
2022-06-21 12:57 ` Dave Blanchard
-- strict thread matches above, loose matches on Subject: below --
2002-12-31 10:24 Martin York
2002-12-30 20:53 Stephen Lindholm
2002-12-30 20:54 ` Neil Booth
2002-12-30 20:54 ` Stephen Lindholm
2003-01-02 21:04 ` Devang Patel
2002-12-30 20:54 ` Neil Booth
2003-01-02 20:42 ` Mike Stump
2003-01-02 21:02 ` Devang Patel
2003-01-04 20:19 ` Zack Weinberg
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=CAFiYyc1M13dxBFok7wwtB6LPJZe68V9UojqWWS4_6B9iWp-XBA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=dave@killthe.net \
--cc=gcc@gcc.gnu.org \
/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).