public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "potswa at mac dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/57714] Newline rendered incorrectly in output
Date: Tue, 25 Jun 2013 20:58:00 -0000	[thread overview]
Message-ID: <bug-57714-4-eo4RZRrZdp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57714-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57714

--- Comment #3 from David Krauss <potswa at mac dot com> ---
See section 9 of the manual:
http://gcc.gnu.org/onlinedocs/gcc-4.8.1/cpp/Preprocessor-Output.html#Preprocessor-Output

The output from the C preprocessor looks much like the input, except that all
preprocessing directive lines have been replaced with blank lines and all
comments with spaces. Long runs of blank lines are discarded.

...

CPP does not insert any whitespace where there was none in the original source,
except where necessary to prevent an accidental token paste.


  parent reply	other threads:[~2013-06-25 20:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 20:36 [Bug preprocessor/57714] New: " potswa at mac dot com
2013-06-25 20:38 ` [Bug preprocessor/57714] " pinskia at gcc dot gnu.org
2013-06-25 20:53 ` potswa at mac dot com
2013-06-25 20:58 ` potswa at mac dot com [this message]
2013-06-25 22:23 ` manu at gcc dot gnu.org
2013-06-25 22:41 ` potswa at mac dot com
2013-06-25 22:43 ` potswa at mac dot com
2013-06-25 22:46 ` potswa at mac dot com
2013-06-25 22:52 ` potswa at mac dot com
2013-06-26  8:38 ` manu at gcc dot gnu.org
2013-06-29  9:18 ` harald at gigawatt dot nl
2013-06-29 11:45 ` harald at gigawatt dot nl
2013-06-29 12:48 ` potswa at mac dot com
2013-06-29 12:58 ` potswa at mac dot com
2013-06-29 14:17 ` potswa at mac dot com

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-57714-4-eo4RZRrZdp@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).