public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65130] [5 Regression] ICE with LTO on valid code on x86_64-linux-gnu
Date: Mon, 02 Mar 2015 06:22:00 -0000	[thread overview]
Message-ID: <bug-65130-4-20L1paxgZS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65130-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65130

--- Comment #8 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Cannot reproduce.

Fixed on mainline by:

commit b9cb01c10d90420929551763dae489c1ef53af93
Author: hubicka <hubicka@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Sun Mar 1 01:08:47 2015 +0000

        * ipa-inline.c (can_inline_edge_p): Match opt_for_fn on inline
        target; also match flag_ipa_devirt.


    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@221084
138bc75d-0d04-0410-961f-82ee72b054a4

Can we close this PR, or is the above patch just papering over the issue?


  parent reply	other threads:[~2015-03-02  6:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  7:26 [Bug lto/65130] New: " su at cs dot ucdavis.edu
2015-02-20  7:40 ` [Bug lto/65130] [5 Regression] " rguenth at gcc dot gnu.org
2015-02-25 21:32 ` aldyh at gcc dot gnu.org
2015-02-25 21:47 ` aldyh at gcc dot gnu.org
2015-02-25 22:48 ` ktietz at gcc dot gnu.org
2015-02-25 22:54 ` ktietz at gcc dot gnu.org
2015-02-26  5:34 ` aldyh at gcc dot gnu.org
2015-03-01 23:45 ` hubicka at gcc dot gnu.org
2015-03-02  6:22 ` aldyh at gcc dot gnu.org [this message]
2015-03-02  7:05 ` hubicka at gcc dot gnu.org
2015-03-02  7:49 ` hubicka at gcc dot gnu.org
2015-03-02  8:06 ` hubicka at ucw dot cz
2015-03-02 11:25 ` ktietz at gcc dot gnu.org
2015-03-02 20:31 ` hubicka at gcc dot gnu.org
2015-03-02 21:59 ` hubicka 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-65130-4-20L1paxgZS@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).