public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/48248] [4.5 Regression] Wrong error message location when compiling preprocessed code
Date: Tue, 26 Apr 2011 10:17:00 -0000	[thread overview]
Message-ID: <bug-48248-4-n6dlJ0m0gw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48248-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-04-26 10:14:37 UTC ---
Author: rguenth
Date: Tue Apr 26 10:14:34 2011
New Revision: 172959

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172959
Log:
2011-04-26  Richard Guenther  <rguenther@suse.de>

    PR preprocessor/48248
    * c-ppoutput.c (maybe_print_line): Always optimize newlines
    for output size with -P.

Modified:
    trunk/gcc/c-family/ChangeLog
    trunk/gcc/c-family/c-ppoutput.c


      parent reply	other threads:[~2011-04-26 10:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  9:27 [Bug preprocessor/48248] New: " joerg.richter@pdv-fs.de
2011-03-23 10:05 ` [Bug preprocessor/48248] [4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-03-28 14:05 ` jakub at gcc dot gnu.org
2011-03-28 14:26 ` joerg.richter@pdv-fs.de
2011-03-28 16:40 ` jakub at gcc dot gnu.org
2011-03-28 19:46 ` jakub at gcc dot gnu.org
2011-03-29 20:31 ` jakub at gcc dot gnu.org
2011-03-29 20:39 ` jakub at gcc dot gnu.org
2011-03-29 21:14 ` [Bug preprocessor/48248] [4.5 " jakub at gcc dot gnu.org
2011-04-10 10:45 ` rguenth at gcc dot gnu.org
2011-04-19  9:14 ` rguenth at gcc dot gnu.org
2011-04-19  9:21 ` rguenth at gcc dot gnu.org
2011-04-19  9:36 ` rguenth at gcc dot gnu.org
2011-04-26 10:17 ` rguenth at gcc dot gnu.org [this message]

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-48248-4-n6dlJ0m0gw@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).