public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neil at daikokuya dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/19836] -E -dD includes predefined macros
Date: Thu, 10 Feb 2005 01:13:00 -0000 [thread overview]
Message-ID: <20050209224846.21606.qmail@sourceware.org> (raw)
In-Reply-To: <20050209061037.19836.jason@catapult.com>
------- Additional Comments From neil at daikokuya dot co dot uk 2005-02-09 22:48 -------
Subject: Re: -E -dD includes predefined macros
jason at catapult dot com wrote:-
> Where did you read this? This is what is written in the CPP and GCC manpages,
> and the GCC online docs.
>
> D - Like M except in two respects: it does not include the predefined macros,
> and it outputs both the #define directives and the result of preprocessing. Both
> kinds of output go to the standard output file.
>
> Neil, thanks for the suggestion, it removed all of them except for #define
> __STDC_HOSTED__ 1, which I can take out with sed.
OK, so 2 bugs here then 8-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19836
next prev parent reply other threads:[~2005-02-09 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 10:15 [Bug preprocessor/19836] New: " jason at catapult dot com
2005-02-09 10:19 ` [Bug preprocessor/19836] " pinskia at gcc dot gnu dot org
2005-02-09 11:06 ` jason at catapult dot com
2005-02-09 17:31 ` Neil Booth
2005-02-09 12:41 ` pinskia at gcc dot gnu dot org
2005-02-09 17:35 ` neil at daikokuya dot co dot uk
2005-02-10 1:13 ` jason at catapult dot com
2005-02-10 1:13 ` neil at daikokuya dot co dot uk [this message]
2005-02-10 2:21 ` jason at catapult dot com
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=20050209224846.21606.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).