public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63569] [5.0 Regression] Wrong code with volatile and ICF
Date: Fri, 21 Nov 2014 08:01:00 -0000 [thread overview]
Message-ID: <bug-63569-4-Jj4npAhnPN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63569-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63569
--- Comment #3 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Any progress with fixing this bug? It still breaks building the
Linux kernel with 5.0:
net/core/dev.c: In function ‘dev_change_net_namespace.part.22’:
net/core/dev.c:7285:1: internal compiler error: in verify_ssa, at
tree-ssa.c:939
subsys_initcall(net_dev_init);
^
>From gcc-bugs-return-467883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 21 08:04:19 2014
Return-Path: <gcc-bugs-return-467883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32757 invoked by alias); 21 Nov 2014 08:04:19 -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 32720 invoked by uid 48); 21 Nov 2014 08:04:15 -0000
From: "zhenqiang.chen at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61225] [5 Regression] Several new failures after r210458 on x86_64-*-* with -m32
Date: Fri, 21 Nov 2014 08:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zhenqiang.chen at arm dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61225-4-0icHQKMzu3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61225-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61225-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-11/txt/msg02355.txt.bz2
Content-length: 178
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida225
--- Comment #15 from Zhenqiang Chen <zhenqiang.chen at arm dot com> ---
Thank you for the reminder. I will rework the patch.
next prev parent reply other threads:[~2014-11-21 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 6:49 [Bug tree-optimization/63569] New: " pinskia at gcc dot gnu.org
2014-10-17 6:51 ` [Bug tree-optimization/63569] " pinskia at gcc dot gnu.org
2014-10-17 22:28 ` pinskia at gcc dot gnu.org
2014-11-11 6:42 ` trippels at gcc dot gnu.org
2014-11-21 8:01 ` trippels at gcc dot gnu.org [this message]
2014-11-21 11:26 ` [Bug ipa/63569] " marxin at gcc dot gnu.org
2014-11-21 12:48 ` marxin at gcc dot gnu.org
2014-11-26 23:50 ` pinskia at gcc dot gnu.org
2014-12-02 13:26 ` pinskia at gcc dot gnu.org
2014-12-12 10:30 ` trippels at gcc dot gnu.org
2014-12-19 12:41 ` marxin 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-63569-4-Jj4npAhnPN@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).