public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/64043] [5 Regression] ICE (segfault) with LTO: in tree_check/tree.h:2758 get_binfo_at_offset/tree.c:11914
Date: Wed, 14 Jan 2015 06:37:00 -0000	[thread overview]
Message-ID: <bug-64043-4-I1pPaH157s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64043-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Unforutnately it is a bit difficult without Haswell machine. Would be possible
to profile it and post the difference in internal loops?
Possibly the target option node is not streamed fully and some flags are
getting lost, though I do not see how that can happen...


  parent reply	other threads:[~2015-01-14  6:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24  9:59 [Bug lto/64043] New: " burnus at gcc dot gnu.org
2014-12-02 21:04 ` [Bug lto/64043] " hubicka at gcc dot gnu.org
2014-12-02 21:08 ` hubicka at gcc dot gnu.org
2014-12-02 21:20 ` jason at gcc dot gnu.org
2014-12-12 15:41 ` burnus at gcc dot gnu.org
2014-12-12 15:43 ` burnus at gcc dot gnu.org
2014-12-12 19:01 ` hubicka at gcc dot gnu.org
2014-12-15  3:42 ` hubicka at gcc dot gnu.org
2014-12-15 22:36 ` hubicka at gcc dot gnu.org
2014-12-16 11:22 ` schwab@linux-m68k.org
2014-12-17 14:29 ` dominiq at lps dot ens.fr
2014-12-22 15:03 ` izamyatin at gmail dot com
2014-12-22 15:17 ` hubicka at ucw dot cz
2014-12-22 15:36 ` izamyatin at gmail dot com
2015-01-12  7:47 ` izamyatin at gmail dot com
2015-01-14  6:37 ` hubicka at gcc dot gnu.org [this message]
2015-01-29  7:17 ` 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-64043-4-I1pPaH157s@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).