public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/64374] [5 Regression] LTO ICE in extract_insn, at recog.c:2327
Date: Wed, 25 Feb 2015 10:35:00 -0000	[thread overview]
Message-ID: <bug-64374-4-G6D5Ape294@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64374-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Dmitry G. Dyachenko <dimhen at gmail dot com> ---
(In reply to Jakub Jelinek from comment #14)
> So, can the reporter or anyone else still reproduce a problem in this area
> or can it be considered fixed?

last FAIL for me r219878
first PASS for me r219927
r220888 PASS for me

original issue with unreduced code go away starting r219927


  parent reply	other threads:[~2015-02-25  9:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22  8:53 [Bug lto/64374] New: [5.0 regression] " dimhen at gmail dot com
2014-12-22  9:08 ` [Bug lto/64374] " pinskia at gcc dot gnu.org
2014-12-22 11:03 ` dimhen at gmail dot com
2014-12-22 11:18 ` dimhen at gmail dot com
2015-01-09 11:20 ` rguenth at gcc dot gnu.org
2015-01-10 17:52 ` dimhen at gmail dot com
2015-01-13 10:54 ` rguenth at gcc dot gnu.org
2015-01-13 15:08 ` jakub at gcc dot gnu.org
2015-01-18 22:51 ` hubicka at gcc dot gnu.org
2015-02-20  7:59 ` [Bug lto/64374] [5 Regression] " jakub at gcc dot gnu.org
2015-02-24 15:09 ` jakub at gcc dot gnu.org
2015-02-24 19:43 ` jakub at gcc dot gnu.org
2015-02-25  9:44 ` jakub at gcc dot gnu.org
2015-02-25  9:51 ` jakub at gcc dot gnu.org
2015-02-25 10:35 ` dimhen at gmail dot com [this message]
2015-02-26 14:17 ` jakub 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-64374-4-G6D5Ape294@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).