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/5289: "cpp -traditional" inserts spurious line breaks Date: Sun, 06 Jan 2002 05:16:00 -0000 [thread overview] Message-ID: <200201061309.g06D93t14025@lilypond.tat.physik.uni-tuebingen.de> (raw) >Number: 5289 >Category: preprocessor >Synopsis: "cpp -traditional" inserts spurious line breaks >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Sun Jan 06 05:16: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: I use cpp to preprocess Fortran 77 code. I call cpp as "cpp -traditional", and I find that cpp inserts spurious line breaks under certain circumstances. cpp from gcc 2.95.3 works fine under the same circumstances. >How-To-Repeat: The following three lines of source code (the first line ends with the backslash) (note the second, empty line) #define a b\ (a) get wrongly preprocessed into the three lines (b ) I think that the result should consist of two lines only, namely (b) without the line break before the closing paren. The above constellation appears in automatically generated code. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-01-06 13:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-06 5:16 schnetter [this message] 2002-01-06 7:42 rodrigc 2002-01-06 8:56 Erik Schnetter 2002-01-06 9:04 rodrigc 2002-01-06 9:26 Erik Schnetter 2002-01-06 9:34 rodrigc
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=200201061309.g06D93t14025@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: 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).