public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60419] [4.8/4.9 Regression] ICE Segmentation fault
Date: Tue, 18 Mar 2014 17:20:00 -0000 [thread overview]
Message-ID: <bug-60419-4-w4TOJDPt89@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60419-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60419
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |trippels at gcc dot gnu.org
--- Comment #9 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Created attachment 32382
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32382&action=edit
reduced testcase
Here's a reduced testcase that segfaults also on x86_64.
markus@x4 tmp % g++ -std=c++11 -c -O2 -c test.ii
ASAN:SIGSEGV
=================================================================
==17160==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000010 (pc
0x000000d9b9b7 sp 0x7fff7ac203c0 bp 0x0fffef5840a0 T0)
#0 0xd9b9b6 in cgraph_function_node(cgraph_node*, availability*)
../../gcc/gcc/cgraph.c:2966
#1 0x25e6923 in propagate_pure_const ../../gcc/gcc/ipa-pure-const.c:1185
#2 0x25e6923 in propagate ../../gcc/gcc/ipa-pure-const.c:1483
#3 0x25e6923 in execute ../../gcc/gcc/ipa-pure-const.c:1536
#4 0x14b93cd in execute_one_pass(opt_pass*) ../../gcc/gcc/passes.c:2229
#5 0x14badd0 in execute_ipa_pass_list(opt_pass*)
../../gcc/gcc/passes.c:2607
#6 0xdb2bb1 in ipa_passes ../../gcc/gcc/cgraphunit.c:2084
#7 0xdb2bb1 in compile() ../../gcc/gcc/cgraphunit.c:2174
#8 0xdb484a in finalize_compilation_unit() ../../gcc/gcc/cgraphunit.c:2329
#9 0x84561a in cp_write_global_declarations() ../../gcc/gcc/cp/decl2.c:4610
#10 0x16aa252 in compile_file ../../gcc/gcc/toplev.c:562
#11 0x16af0db in do_compile ../../gcc/gcc/toplev.c:1914
#12 0x16af0db in toplev_main(int, char**) ../../gcc/gcc/toplev.c:1990
#13 0x7ff8fae69faf in __libc_start_main (/lib/libc.so.6+0x1ffaf)
#14 0x5d9460
(/var/tmp/gcc_sani/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/cc1plus+0x5d9460)
next prev parent reply other threads:[~2014-03-18 17:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 23:04 [Bug tree-optimization/60419] New: [4.8 / 4.9 " doko at gcc dot gnu.org
2014-03-05 8:34 ` [Bug middle-end/60419] [4.8/4.9 " doko at gcc dot gnu.org
2014-03-05 9:06 ` y.gribov at samsung dot com
2014-03-05 9:29 ` rguenth at gcc dot gnu.org
2014-03-09 21:41 ` jakub at gcc dot gnu.org
2014-03-10 9:02 ` jakub at gcc dot gnu.org
2014-03-12 16:24 ` jakub at gcc dot gnu.org
2014-03-13 9:00 ` jakub at gcc dot gnu.org
2014-03-18 10:59 ` jakub at gcc dot gnu.org
2014-03-18 17:20 ` trippels at gcc dot gnu.org [this message]
2014-03-18 17:37 ` trippels at gcc dot gnu.org
2014-03-19 10:44 ` jamborm at gcc dot gnu.org
2014-03-20 9:22 ` jakub at gcc dot gnu.org
2014-03-20 9:37 ` trippels at gcc dot gnu.org
2014-03-20 9:38 ` trippels at gcc dot gnu.org
2014-03-20 9:55 ` trippels at gcc dot gnu.org
2014-03-20 10:15 ` jakub at gcc dot gnu.org
2014-03-20 16:28 ` jamborm at gcc dot gnu.org
2014-03-21 12:48 ` jamborm at gcc dot gnu.org
2014-03-21 14:27 ` [Bug middle-end/60419] [4.8 " jakub at gcc dot gnu.org
2014-03-26 13:48 ` jamborm at gcc dot gnu.org
2014-03-26 13:50 ` jamborm 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-60419-4-w4TOJDPt89@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).