public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46130] [4.6 Regression] ICE: SIGSEGV in walk_stmt_load_store_addr_ops (gimple.c:4894) with -O2 -fno-tree-dce Date: Tue, 16 Nov 2010 01:05:00 -0000 [thread overview] Message-ID: <bug-46130-4-Wih4e1iPkj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46130-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46130 --- Comment #6 from Zdenek Sojka <zsojka at seznam dot cz> 2010-11-16 00:52:52 UTC --- Created attachment 22414 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22414 another simple testcase This one needs -flto too: $ gcc -O2 -flto -fno-tree-dce testcase.c ==9353== Invalid read of size 2 ==9353== at 0x710735: walk_stmt_load_store_addr_ops (gimple.c:5024) ==9353== by 0xAC5C12: rebuild_cgraph_edges (cgraphbuild.c:474) ==9353== by 0x7BCA0E: execute_one_pass (passes.c:1560) ==9353== by 0x7BCCD4: execute_pass_list (passes.c:1615) ==9353== by 0x7BBEFB: do_per_function_toporder (passes.c:1153) ==9353== by 0x7BD185: execute_ipa_pass_list (passes.c:1932) ==9353== by 0xACAD67: cgraph_optimize (cgraphunit.c:1694) ==9353== by 0xACAF29: cgraph_finalize_compilation_unit (cgraphunit.c:1015) ==9353== by 0x4D7D8B: c_write_global_declarations (c-decl.c:9837) ==9353== by 0x8A9405: toplev_main (toplev.c:885) ==9353== by 0x6376BBC: (below main) (in /lib64/libc-2.11.2.so) ==9353== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==9353== testcase.c: In function 'foo': testcase.c:4:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions.
next prev parent reply other threads:[~2010-11-16 0:53 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-22 13:35 [Bug tree-optimization/46130] New: " zsojka at seznam dot cz 2010-10-22 13:49 ` [Bug tree-optimization/46130] " zsojka at seznam dot cz 2010-10-22 13:58 ` hjl.tools at gmail dot com 2010-10-22 14:05 ` zsojka at seznam dot cz 2010-10-22 14:08 ` rguenth at gcc dot gnu.org 2010-10-26 0:38 ` jakub at gcc dot gnu.org 2010-11-02 12:50 ` rguenth at gcc dot gnu.org 2010-11-16 1:05 ` zsojka at seznam dot cz [this message] 2011-01-19 16:41 ` jakub at gcc dot gnu.org 2011-01-19 17:31 ` jakub at gcc dot gnu.org 2011-01-19 19:31 ` jakub at gcc dot gnu.org 2011-01-20 12:23 ` jakub at gcc dot gnu.org 2011-01-20 12:26 ` jakub 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-46130-4-Wih4e1iPkj@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).