public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/65908] [5/6 Regression] ICE: in expand_thunk, at cgraphunit.c:1700 Date: Tue, 12 May 2015 14:08:00 -0000 [thread overview] Message-ID: <bug-65908-4-R9jopVhm5T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65908-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65908 --- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> --- Created attachment 35533 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35533&action=edit Suggested fix I've been testing following patch for 5.1.0 branch. I'm wondering if comparison of just TYPE_ARG_TYPES is sufficient? >From gcc-bugs-return-486142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 12 14:17:51 2015 Return-Path: <gcc-bugs-return-486142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 115429 invoked by alias); 12 May 2015 14:17:51 -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 115402 invoked by uid 48); 12 May 2015 14:17:47 -0000 From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66089] [6 Regression] elemental dependency mishandling when derived types are involved Date: Tue, 12 May 2015 14:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mikael at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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-66089-4-FyXrA823yj@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66089-4@http.gcc.gnu.org/bugzilla/> References: <bug-66089-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-05/txt/msg00982.txt.bz2 Content-length: 390 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf089 --- Comment #4 from Mikael Morin <mikael at gcc dot gnu.org> --- (In reply to Dominique d'Humieres from comment #3) > The code in comment 0 does not abort at run time up to revision r222352 > (2015-04-23), but does so at r222398 (2015-04-24), likely r222361. Yes, probably the change in gfc_add_loop_ss_code (which comment #1 removes).
next prev parent reply other threads:[~2015-05-12 14:08 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-27 17:34 [Bug c++/65908] New: internal compiler error: in expand_thunk mark at noffle dot net 2015-04-27 17:47 ` [Bug c++/65908] " mark at noffle dot net 2015-04-27 17:59 ` [Bug ipa/65908] [5/6 Regression] ICE: in expand_thunk, at cgraphunit.c:1700 trippels at gcc dot gnu.org 2015-04-27 22:29 ` jakub at gcc dot gnu.org 2015-04-27 23:09 ` jakub at gcc dot gnu.org 2015-04-28 8:16 ` jakub at gcc dot gnu.org 2015-05-11 11:50 ` hubicka at gcc dot gnu.org 2015-05-12 14:08 ` marxin at gcc dot gnu.org [this message] 2015-05-12 19:44 ` hubicka at gcc dot gnu.org 2015-06-17 13:24 ` jakub at gcc dot gnu.org 2015-06-17 13:29 ` marxin at gcc dot gnu.org 2015-06-22 7:12 ` hubicka at gcc dot gnu.org 2015-07-03 9:11 ` [Bug ipa/65908] [5 " rguenth at gcc dot gnu.org 2015-07-16 9:15 ` rguenth 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-65908-4-R9jopVhm5T@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).