public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: schnetter@uni-tuebingen.de
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/5288: "cpp -traditional -dD" does not output preprocessing result
Date: Sun, 06 Jan 2002 04:46:00 -0000 [thread overview]
Message-ID: <200201061245.g06CjUx13476@lilypond.tat.physik.uni-tuebingen.de> (raw)
>Number: 5288
>Category: preprocessor
>Synopsis: "cpp -traditional -dD" does not output preprocessing result
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jan 06 04:46:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Erik Schnetter
>Release: 3.0.3
>Organization:
Theoretische Astrophysik Tuebingen
>Environment:
System: Linux lilypond 2.4.10-4GB #1 Tue Sep 25 12:33:54 GMT 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.0.3/configure --prefix=/home/eschnett/gcc
>Description:
When calling cpp as "cpp -traditional -dD", it is supposed to output
both the #defines and the result of the precprocessing. However, with
these options cpp outputs only the #defines and does not output the
result of the preprocessing. (The option combination "cpp -dD"
(without the "-traditional") works fine.)
>How-To-Repeat:
>Fix:
A work around is to run cpp twice, once as "cpp -traditional -dD" to
get the #defines in effect, and once as "cpp -traditional" to get the
result of the preprocessing.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-01-06 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 4:46 schnetter [this message]
2002-01-06 7:43 rodrigc
2002-01-06 9:06 Erik Schnetter
2002-01-06 9:39 rodrigc
2002-06-18 3:38 neil
2002-06-20 14:50 neil
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=200201061245.g06CjUx13476@lilypond.tat.physik.uni-tuebingen.de \
--to=schnetter@uni-tuebingen.de \
--cc=gcc-gnats@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).