public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Erik Schnetter <schnetter@uni-tuebingen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/5288: "cpp -traditional -dD" does not output preprocessing result Date: Sun, 06 Jan 2002 09:06:00 -0000 [thread overview] Message-ID: <20020106170601.27273.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/5288; it has been noted by GNATS. From: Erik Schnetter <schnetter@uni-tuebingen.de> To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: preprocessor/5288: "cpp -traditional -dD" does not output preprocessing result Date: Sun, 6 Jan 2002 17:57:24 +0100 On Sunday 06 January 2002 16:43, rodrigc@gcc.gnu.org wrote: > Synopsis: "cpp -traditional -dD" does not output preprocessing result > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Sun Jan 6 07:43:21 2002 > State-Changed-Why: > Can you submit an example, with a description? > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc& >pr=5288 Sorry, I thought my description was clear. The example is really simple, so I omitted it. Try a source file that has a single line only, consiting of a single character "a" only. According to the docs, the output should contain the same line, in addition to several #define statements. But the output has only #define statements. -erik -- Erik Schnetter <schnetter@uni-tuebingen.de>
next reply other threads:[~2002-01-06 17:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-06 9:06 Erik Schnetter [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-20 14:50 neil 2002-06-18 3:38 neil 2002-01-06 9:39 rodrigc 2002-01-06 7:43 rodrigc 2002-01-06 4:46 schnetter
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=20020106170601.27273.qmail@sources.redhat.com \ --to=schnetter@uni-tuebingen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).