public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57416] internal compiler error: in gimple_expand_cfg, at cfgexpand.c:4575 Date: Sat, 25 May 2013 18:26:00 -0000 [thread overview] Message-ID: <bug-57416-4-PnLtqymXcj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57416-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57416 --- Comment #4 from Daniel Krügler <daniel.kruegler at googlemail dot com> --- If you remove the still existing member initializer in func1, does the ICE still exist? (On 4.9 after removal of that initializer I could compile and run the program). Are all the compiler flags necessary to reproduce the ICE, or will e.g. the combination of -Wall -std=c++11 suffice to produce the ICE? >From gcc-bugs-return-423159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 25 18:27:32 2013 Return-Path: <gcc-bugs-return-423159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 22836 invoked by alias); 25 May 2013 18:27:32 -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 22796 invoked by uid 48); 25 May 2013 18:27:29 -0000 From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57416] internal compiler error: in gimple_expand_cfg, at cfgexpand.c:4575 Date: Sat, 25 May 2013 18:27: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.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daniel.kruegler at googlemail 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: Message-ID: <bug-57416-4-WMmLr63Af1@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-57416-4@http.gcc.gnu.org/bugzilla/> References: <bug-57416-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: 2013-05/txt/msg01832.txt.bz2 Content-length: 290 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57416 --- Comment #5 from Daniel Krügler <daniel.kruegler at googlemail dot com> --- (In reply to Daniel Krügler from comment #4) We had a clash here, but except for my first observation the remaining questions are still relevant. >From gcc-bugs-return-423160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 25 18:42:50 2013 Return-Path: <gcc-bugs-return-423160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29778 invoked by alias); 25 May 2013 18:42:50 -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 29753 invoked by uid 48); 25 May 2013 18:42:47 -0000 From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57417] New: hang on volatile int array Date: Sat, 25 May 2013 18:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: su at cs dot ucdavis.edu 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-57417-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: 2013-05/txt/msg01833.txt.bz2 Content-length: 837 http://gcc.gnu.org/bugzilla/show_bug.cgi?idW417 Bug ID: 57417 Summary: hang on volatile int array Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: su at cs dot ucdavis.edu The following code causes gcc trunk (and the 4.7 & 4.8 branches) to hang at -O1 or above. This seems to be different from 57381, but perhaps related. $ gcc-trunk -v Target: x86_64-unknown-linux-gnu gcc version 4.9.0 20130525 (experimental) [trunk revision 199323] (GCC) $ gcc-trunk -m32 -O0 -c small.c $ gcc-trunk -m32 -O1 -c small.c ^C $ cat small.c int a, b, c; void foo () { volatile int d[1]; b = 0; for (;; a--) c = (int)&d[b]; }
next prev parent reply other threads:[~2013-05-25 18:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-25 17:02 [Bug c++/57416] New: " FBergemann at web dot de 2013-05-25 17:59 ` [Bug c++/57416] " daniel.kruegler at googlemail dot com 2013-05-25 18:24 ` FBergemann at web dot de 2013-05-25 18:26 ` daniel.kruegler at googlemail dot com [this message] 2013-05-25 19:55 ` FBergemann at web dot de 2013-05-27 8:27 ` rguenth at gcc dot gnu.org 2013-08-12 22:53 ` paolo.carlini at oracle dot com 2013-08-12 22:55 ` paolo.carlini at oracle dot com
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-57416-4-PnLtqymXcj@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: linkBe 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).