public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "octoploid at yandex dot com" <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 06:16:00 -0000 [thread overview] Message-ID: <bug-59265-4-aBnfP4tVUx@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 #6 from Markus Trippelsdorf <octoploid at yandex dot com> --- It now segfaults in ipa_profile_generate_summary: ==9510==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000028 (pc 0x00000120aff0 sp 0x7fff4fe6add0 bp 0x606000210080 T0) #0 0x120afef in ipa_profile_generate_summary() /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/ipa-profile.c:216 #1 0x142d44f in execute_ipa_summary_passes(ipa_opt_pass_d*) /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/passes.c:2013 #2 0xd6bbbe in ipa_passes /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/cgraphunit.c:2022 #3 0xd6bbbe in compile() /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/cgraphunit.c:2126 #4 0xd6c62a in finalize_compilation_unit() /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/cgraphunit.c:2280 #5 0x81a98a in cp_write_global_declarations() /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/cp/decl2.c:4431 #6 0x1613bd4 in compile_file() /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/toplev.c:561 #7 0x1618663 in do_compile /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/toplev.c:1893 #8 0x1618663 in toplev_main(int, char**) /var/tmp/gcc_build_dir/gcc/../../gcc/gcc/toplev.c:1969 #9 0x7f764d115f8f in __libc_start_main (/lib/libc.so.6+0x1ff8f) #10 0x5b46b0 in _start (/var/tmp/gcc_sani/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/cc1plus+0x5b46b0)
next prev parent reply other threads:[~2013-12-16 6:16 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 [this message] 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 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-aBnfP4tVUx@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: linkBe 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).