public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/64968] Upgrade GCC Bugzilla to 5.0
Date: Sat, 18 Apr 2015 18:30:00 -0000	[thread overview]
Message-ID: <bug-64968-4-RL5iHhw2JD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64968-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Frédéric Buclin <LpSolit at netscape dot net> ---
Created attachment 35354
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35354&action=edit
GCC extension for 5.0, v2

And the corresponding new extension.
>From gcc-bugs-return-483985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 18 18:47:46 2015
Return-Path: <gcc-bugs-return-483985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65149 invoked by alias); 18 Apr 2015 18:47:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65115 invoked by uid 48); 18 Apr 2015 18:47:41 -0000
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65801] [5/6 Regression] Allow -Wno-narrowing to silence stricter C++11 narrowing rules
Date: Sat, 18 Apr 2015 18:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: trippels at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc short_desc everconfirmed
Message-ID: <bug-65801-4-3I78jRJMo7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg01537.txt.bz2
Content-length: 1312

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

Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-04-18
                 CC|                            |trippels at gcc dot gnu.org
            Summary|Allow -Wno-narrowing to     |[5/6 Regression] Allow
                   |silence stricter C++11      |-Wno-narrowing to silence
                   |narrowing rules             |stricter C++11 narrowing
                   |                            |rules
     Ever confirmed|0                           |1

--- Comment #1 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Yes. This also breaks building Chromium.

markus@x4 ~ % echo "int main () {int i = { 0xFFFFFFFF };}" | g++ -std=c++11
-Wno-narrowing -x c++ -
<stdin>: In function ‘int main()’:
<stdin>:1:35: error: narrowing conversion of ‘4294967295u’ from ‘unsigned int’
to ‘int’ inside { }

While the standard is clear that this is an error,
accepting -Wno-narrowing as in 4.8, 4.9 and clang looks acceptable to me.
>From gcc-bugs-return-483986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 18 19:04:52 2015
Return-Path: <gcc-bugs-return-483986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5345 invoked by alias); 18 Apr 2015 19:04:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5312 invoked by uid 48); 18 Apr 2015 19:04:48 -0000
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65802] [6 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2335
Date: Sat, 18 Apr 2015 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dimhen at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-65802-4-O4Pup37Odb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65802-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65802-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg01538.txt.bz2
Content-length: 415

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide802

Dmitry G. Dyachenko <dimhen at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tom at codesourcery dot com

--- Comment #1 from Dmitry G. Dyachenko <dimhen at gmail dot com> ---
r222168 PASS
r222174 FAIL


  parent reply	other threads:[~2015-04-18 18:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 14:23 [Bug web/64968] New: " LpSolit at netscape dot net
2015-02-07 14:44 ` [Bug web/64968] " trippels at gcc dot gnu.org
2015-02-09 10:39 ` LpSolit at netscape dot net
2015-02-09 11:43 ` fche at redhat dot com
2015-02-11 14:37 ` LpSolit at netscape dot net
2015-02-11 16:33 ` fche at redhat dot com
2015-02-11 20:46 ` LpSolit at netscape dot net
2015-02-11 20:48 ` LpSolit at netscape dot net
2015-04-18 18:30 ` LpSolit at netscape dot net [this message]
2015-04-27 15:13 ` mikael at gcc dot gnu.org
2015-04-27 17:39 ` fche at redhat dot com
2015-04-27 18:34 ` LpSolit at netscape dot net
2015-04-27 19:47 ` LpSolit at netscape dot net
2015-04-28 16:28 ` trippels at gcc dot gnu.org
2015-04-28 18:26 ` LpSolit at netscape dot net
2015-04-29 12:27 ` LpSolit at netscape dot net
2015-04-29 16:02 ` trippels at gcc dot gnu.org
2015-04-30 13:48 ` trippels at gcc dot gnu.org
2015-04-30 16:34 ` LpSolit at netscape dot net
2015-04-30 20:53 ` LpSolit at netscape dot net
2015-05-01  9:16 ` LpSolit at netscape dot net
2015-05-03  1:00 ` LpSolit at netscape dot net
2015-05-08  6:22 ` trippels at gcc dot gnu.org
2015-05-08  6:46 ` schwab@linux-m68k.org
2015-05-08  6:51 ` trippels at gcc dot gnu.org
2015-05-08 11:02 ` LpSolit at netscape dot net
2015-05-08 18:55 ` LpSolit at netscape dot net
2015-05-08 19:04 ` trippels at gcc dot gnu.org
2015-05-15 14:06 ` LpSolit at netscape dot net
2015-05-26 14:15 ` trippels at gcc dot gnu.org
2015-05-26 17:41 ` fche at redhat dot com
2015-07-13 10:49 ` trippels at gcc dot gnu.org
2015-09-25  9:05 ` trippels at gcc dot gnu.org
2015-09-26 15:28 ` LpSolit at netscape dot net

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-64968-4-RL5iHhw2JD@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).