From: Andreas Schwab <schwab@suse.de>
To: Nathan Sidwell <nathan@acm.org>
Cc: "gcc\@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Deprecate -traditional-cpp?
Date: Thu, 05 Sep 2019 12:33:00 -0000 [thread overview]
Message-ID: <mvmmufi7wio.fsf@suse.de> (raw)
In-Reply-To: <27f8f3cb-693c-0306-138b-dd5bd5ffd995@acm.org> (Nathan Sidwell's message of "Thu, 5 Sep 2019 07:08:20 -0400")
On Sep 05 2019, Nathan Sidwell <nathan@acm.org> wrote:
> Is it time to deprecate traditional preprocessing? It's been 30 years
> since C89. Are (non-compiler) tools that use it still things?
It's probably still used together with -xassembler-with-cpp.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2019-09-05 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 11:08 Nathan Sidwell
2019-09-05 11:16 ` Janne Blomqvist
2019-09-05 14:03 ` Steve Kargl
2019-09-05 14:08 ` Steve Kargl
2019-09-05 15:53 ` Steve Kargl
2019-09-05 19:31 ` Gaius Mulley
2019-09-05 12:33 ` Andreas Schwab [this message]
2019-09-05 12:45 ` Jakub Jelinek
2019-09-05 12:59 ` Florian Weimer
2019-09-05 12:48 ` Florian Weimer
2019-09-05 13:01 ` Martin Jambor
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=mvmmufi7wio.fsf@suse.de \
--to=schwab@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=nathan@acm.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).