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 ipa/59775] [4.9 Regression]  internal compiler error: Segmentation fault
Date: Wed, 15 Jan 2014 21:32:00 -0000	[thread overview]
Message-ID: <bug-59775-4-6fuM13Wvdo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59775-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59775

--- Comment #12 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
OK, thanks for testing. I posted the patch.
How far do we get with libreoffice and LTO now? (I need to move my compilation
setup to new machine, it is on my TODO to get some statistic about
devirtualization there - or any other app that does virtual inheritance)


  parent reply	other threads:[~2014-01-15 21:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 16:53 [Bug c++/59775] New: " nheghathivhistha at gmail dot com
2014-01-12 17:01 ` [Bug c++/59775] " nheghathivhistha at gmail dot com
2014-01-12 17:24 ` nheghathivhistha at gmail dot com
2014-01-12 17:25 ` nheghathivhistha at gmail dot com
2014-01-12 18:57 ` trippels at gcc dot gnu.org
2014-01-12 19:44 ` [Bug ipa/59775] [4.9 Regression] " jakub at gcc dot gnu.org
2014-01-12 22:26 ` hubicka at gcc dot gnu.org
2014-01-12 22:49 ` hubicka at gcc dot gnu.org
2014-01-12 23:37 ` hubicka at ucw dot cz
2014-01-14  8:36 ` nheghathivhistha at gmail dot com
2014-01-14  9:06 ` trippels at gcc dot gnu.org
2014-01-15 21:32 ` hubicka at gcc dot gnu.org [this message]
2014-01-16  8:49 ` nheghathivhistha at gmail dot com
2014-01-17  1:05 ` hubicka at gcc dot gnu.org
2014-01-17  1:07 ` 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-59775-4-6fuM13Wvdo@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).