public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57763] [4.9 Regression]: comp-goto-1.c: ICE verify_flow_info failed, error: EDGE_CROSSING missing across section boundary
Date: Sat, 18 Jan 2014 09:57:00 -0000	[thread overview]
Message-ID: <bug-57763-4-UStEiHE3dG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57763-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #24 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Uroš Bizjak from comment #23)
> (In reply to Jakub Jelinek from comment #22)
> > Created attachment 31868 [details]
> > gcc49-pr57763.patch
> > 
> > Uros, can you please bootstrap/regtest on alpha this updated patch too? 
> > Thanks.
> > Looking at the *.bbpart dump, it seems the increment is desirable.
> 
> Started, complete results will be available in ~10 hours.

This bootstrap/regtest was also OK.
>From gcc-bugs-return-440815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 18 10:03:26 2014
Return-Path: <gcc-bugs-return-440815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7301 invoked by alias); 18 Jan 2014 10:03:26 -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 7258 invoked by uid 48); 18 Jan 2014 10:03:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/59871] [4.7/4.8/4.9 Regression] No unused value warning for comma expression
Date: Sat, 18 Jan 2014 10:03: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: 4.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-59871-4-bTyhtYJR4L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59871-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: 2014-01/txt/msg01957.txt.bz2
Content-length: 971

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY871

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|No unused value warning for |[4.7/4.8/4.9 Regression] No
                   |comma expression            |unused value warning for
                   |                            |comma expression

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Even 3.4.x gave:
pr59871.c:6: warning: left-hand operand of comma expression has no effect
pr59871.c:7: warning: left-hand operand of comma expression has no effect
pr59871.c:8: warning: left-hand operand of comma expression has no effect
pr59871.c:10: warning: left-hand operand of comma expression has no effect
pr59871.c:8: warning: value computed is not used
pr59871.c:10: warning: value computed is not used
so this seems to have regressed in 4.0.


  parent reply	other threads:[~2014-01-18  9:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 17:00 [Bug rtl-optimization/57763] New: " ubizjak at gmail dot com
2013-06-30 22:08 ` [Bug rtl-optimization/57763] " steven at gcc dot gnu.org
2013-07-06 21:49 ` steven at gcc dot gnu.org
2013-07-06 21:57 ` steven at gcc dot gnu.org
2013-07-07 10:58 ` stevenb.gcc at gmail dot com
2013-08-27  9:01 ` ubizjak at gmail dot com
2013-10-30 13:07 ` rguenth at gcc dot gnu.org
2013-12-24 18:52 ` steven at gcc dot gnu.org
2013-12-25  9:19 ` ubizjak at gmail dot com
2014-01-08  9:09 ` ubizjak at gmail dot com
2014-01-15 23:03 ` ubizjak at gmail dot com
2014-01-16 12:11 ` jakub at gcc dot gnu.org
2014-01-16 12:25 ` ubizjak at gmail dot com
2014-01-17  8:17 ` ubizjak at gmail dot com
2014-01-17  9:07 ` ebotcazou at gcc dot gnu.org
2014-01-17  9:32 ` jakub at gcc dot gnu.org
2014-01-17 10:46 ` ubizjak at gmail dot com
2014-01-18  9:57 ` ubizjak at gmail dot com [this message]
2014-01-19 15:31 ` jakub at gcc dot gnu.org
2014-01-19 15:34 ` 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-57763-4-UStEiHE3dG@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).