public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/60150] [4.9 Regression] ICE in function_and_variable_visibility, at ipa.c:1000 Date: Tue, 04 Mar 2014 08:55:00 -0000 [thread overview] Message-ID: <bug-60150-4-ws2TvhTBlR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60150-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60150 --- Comment #5 from Dmitry Gorbachev <d.g.gorbachev at gmail dot com> --- Ok, but there is no «#define XXX» before «#include "pr60150.H"» in pr60150_0.C, which does not seem to be correct. >From gcc-bugs-return-445354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 04 08:59:56 2014 Return-Path: <gcc-bugs-return-445354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 27507 invoked by alias); 4 Mar 2014 08:59:55 -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 27444 invoked by uid 48); 4 Mar 2014 08:59:52 -0000 From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58880] [4.9 Regression] [OOP] ICE on valid with FINAL function and type extension Date: Tue, 04 Mar 2014 08:59: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: 4.9.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: janus 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: cc Message-ID: <bug-58880-4-QiZP4CJ0o2@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-58880-4@http.gcc.gnu.org/bugzilla/> References: <bug-58880-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-03/txt/msg00223.txt.bz2 Content-length: 502 http://gcc.gnu.org/bugzilla/show_bug.cgi?idX880 janus at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #4 from janus at gcc dot gnu.org --- (In reply to Dominique d'Humieres from comment #3) > The Ice starts at r199409. Yes, this was the commit (by Tobias) which enabled the finalization wrapper.
next prev parent reply other threads:[~2014-03-04 8:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-11 18:05 [Bug lto/60150] New: " d.g.gorbachev at gmail dot com 2014-02-12 11:49 ` [Bug lto/60150] " rguenth at gcc dot gnu.org 2014-02-27 9:32 ` rguenth at gcc dot gnu.org 2014-02-28 17:20 ` hubicka at gcc dot gnu.org 2014-03-02 22:20 ` hubicka at gcc dot gnu.org 2014-03-02 22:25 ` hubicka at gcc dot gnu.org 2014-03-04 8:55 ` d.g.gorbachev at gmail dot com [this message] 2014-11-25 22:28 ` d.g.gorbachev at gmail 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-60150-4-ws2TvhTBlR@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).