public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/37549] gcc -E -dD prints predefined macros, contrary to docs Date: Mon, 30 Mar 2009 23:22:00 -0000 [thread overview] Message-ID: <20090330232201.1463.qmail@sourceware.org> (raw) In-Reply-To: <bug-37549-16725@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from tromey at gcc dot gnu dot org 2009-03-30 23:22 ------- Try this. I'll submit it if it regression tests ok. Index: c-ppoutput.c =================================================================== --- c-ppoutput.c (revision 145295) +++ c-ppoutput.c (working copy) @@ -377,6 +380,8 @@ static void cb_define (cpp_reader *pfile, source_location line, cpp_hashnode *node) { + if (line <= BUILTINS_LOCATION) + return; maybe_print_line (line); fputs ("#define ", print.outf); @@ -396,6 +401,8 @@ cb_undef (cpp_reader *pfile ATTRIBUTE_UNUSED, source_location line, cpp_hashnode *node) { + if (line <= BUILTINS_LOCATION) + return; maybe_print_line (line); fprintf (print.outf, "#undef %s\n", NODE_NAME (node)); print.src_line++; -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37549
prev parent reply other threads:[~2009-03-30 23:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-09-17 2:26 [Bug preprocessor/37549] New: " martinrb at google dot com 2008-09-17 3:13 ` Andrew Thomas Pinski 2008-09-17 3:15 ` [Bug preprocessor/37549] " pinskia at gmail dot com 2008-09-17 4:28 ` martinrb at google dot com 2009-03-30 0:40 ` jsm28 at gcc dot gnu dot org 2009-03-30 23:22 ` tromey at gcc dot gnu dot org [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=20090330232201.1463.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: linkBe 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).