public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/59265] [4.9 Regression] Segmentation fault in ipa_note_param_call for -fprofile-use in SPEC CPU2006
Date: Mon, 16 Dec 2013 17:51:00 -0000	[thread overview]
Message-ID: <bug-59265-4-5mtYfGR8Uq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59265-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Jan Hubicka <hubicka at ucw dot cz> ---
> Executing: c++ -o js -Wall -Wpointer-arith -Woverloaded-virtual
> -Werror=return-type -Wtype-limits -Wempty-body -Werror=conversion-null
> -Wsign-compare -Wno-invalid-offsetof -Wcast-align -flto=4 -fprofile-use
> -fprofile-correction -fno-reorder-blocks-and-partition -march=native -fno-rtti
> -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED
> -O3 -fomit-frame-pointer /var/tmp/moz-build-dir/js/src/shell/tmpD2q9gU.list
> -lpthread -Wl,-z,noexecstack -Wl,-z,text -Wl,--build-id
> -Wl,-rpath-link,../../../dist/bin
> -Wl,-rpath-link,/var/tmp/moz-build-dir/dist/lib -L../../../dist/bin
> -L../../../dist/lib -L/var/tmp/moz-build-dir/dist/lib -lnspr4 -lplc4 -lplds4
> ../libjs_static.a -lz -Wl,--whole-archive ../../../dist/lib/libmozglue.a
> -Wl,--no-whole-archive -rdynamic -lm -ldl -lffi
> /var/tmp/moz-build-dir/js/src/shell/tmpD2q9gU.list:
>     INPUT("Unified_cpp_shell0.o")
>     INPUT("../editline/Unified_c_editline0.o")
> 
> In member function ???extractBetween???:
> lto1: fatal error: Cgraph edge statement index out of range
> compilation terminated.

This looks like some kind of LTO streaming corruption.  Are you sure you
rebuilt everything with updated compiler?

Honza


  parent reply	other threads:[~2013-12-16 17:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 17:57 [Bug c++/59265] New: " marxin.liska at gmail dot com
2013-11-25  9:19 ` [Bug ipa/59265] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-12-14 13:39 ` octoploid at yandex dot com
2013-12-14 20:35 ` octoploid at yandex dot com
2013-12-15 16:00 ` hubicka at gcc dot gnu.org
2013-12-15 16:32 ` hubicka at gcc dot gnu.org
2013-12-15 22:19 ` hubicka at gcc dot gnu.org
2013-12-16  6:16 ` octoploid at yandex dot com
2013-12-16  8:02 ` octoploid at yandex dot com
2013-12-16  8:48 ` octoploid at yandex dot com
2013-12-16 11:14 ` hubicka at gcc dot gnu.org
2013-12-16 12:04 ` octoploid at yandex dot com
2013-12-16 13:20 ` hubicka at gcc dot gnu.org
2013-12-16 13:37 ` hubicka at gcc dot gnu.org
2013-12-16 13:41 ` hubicka at gcc dot gnu.org
2013-12-16 15:08 ` octoploid at yandex dot com
2013-12-16 17:51 ` hubicka at ucw dot cz [this message]
2013-12-16 20:32 ` trippels at gcc dot gnu.org
2013-12-16 21:13 ` hubicka at ucw dot cz
2013-12-16 21:32 ` trippels at gcc dot gnu.org
2013-12-16 21:50 ` hubicka at ucw dot cz
2013-12-17 13:01 ` trippels at gcc dot gnu.org
2013-12-17 21:25 ` trippels at gcc dot gnu.org
2013-12-18  9:14 ` trippels 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-59265-4-5mtYfGR8Uq@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).