public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/48071] New: Blank line after 'all warnings being treated as errors'
Date: Fri, 11 Mar 2011 13:27:00 -0000	[thread overview]
Message-ID: <bug-48071-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: Blank line after 'all warnings being treated as
                    errors'
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dnovillo@gcc.gnu.org


After -Werror is triggered, we are now emitting an extra blank line
that we were not emitting before.

$ cat a.cc
char c = 257;
$ g++-4.4.3 -c -o /dev/null -Werror a.cc
cc1plus: warnings being treated as errors
a.cc:1: error: overflow in implicit constant conversion
$

But with trunk, I get:

$ ~/gcc-trunk/native/bin/g++ -c -o /dev/null -Werror a.cc
a.cc:1:10: error: overflow in implicit constant conversion [-Werror=overflow]
cc1plus: all warnings being treated as errors
[... extra blank line ...]
$


             reply	other threads:[~2011-03-11 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 13:27 dnovillo at gcc dot gnu.org [this message]
2012-02-01 19:42 ` [Bug middle-end/48071] [4.6/4.7 Regression] " pinskia at gcc dot gnu.org
2012-02-02 15:19 ` jakub at gcc dot gnu.org
2012-02-02 15:20 ` jakub at gcc dot gnu.org
2012-02-02 20:47 ` jakub at gcc dot gnu.org
2012-02-02 20:48 ` [Bug middle-end/48071] [4.6 " jakub at gcc dot gnu.org
2012-02-09 17:29 ` jakub at gcc dot gnu.org
2012-02-09 17:49 ` jakub 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-48071-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).