public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mike at flyn dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67266] New: Use of "cpp -P ..." collapses multiple blank lines
Date: Wed, 19 Aug 2015 00:43:00 -0000	[thread overview]
Message-ID: <bug-67266-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67266

            Bug ID: 67266
           Summary: Use of "cpp -P ..." collapses multiple blank lines
           Product: gcc
           Version: 5.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mike at flyn dot org
  Target Milestone: ---

I am using:

       cpp -C -P -nostdinc -std=c99 -Werror

to process something that is not C. Everything works, except that one side
effect of "-P" is that consecutive newlines are compressed into one.

For example,

$ cpp -P
x


x

outputs

x
x

I have not found documentation of this behavior. My hunch is that -P should not
behave this way because the man page states, "this might be useful when running
the preprocessor on something that is not C code." I would think that users
employing cpp to process non-C would expect newlines to be preserved.

I previously brought this up on the GCC mailing list. See
https://gcc.gnu.org/ml/gcc-help/2015-08/msg00069.html.


             reply	other threads:[~2015-08-19  0:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  0:43 mike at flyn dot org [this message]
2015-08-19  1:27 ` [Bug preprocessor/67266] " pinskia at gcc dot gnu.org
2015-08-19  1:46 ` mike at flyn dot org
2015-08-19  2:08 ` msebor at gcc dot gnu.org

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=bug-67266-4@http.gcc.gnu.org/bugzilla/ \
    --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).