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] New: [4.6 Regression] ICE: SIGSEGV in walk_stmt_load_store_addr_ops (gimple.c:4894) with -O2 -fno-tree-dce Date: Fri, 22 Oct 2010 13:35:00 -0000 [thread overview] Message-ID: <bug-46130-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46130 Summary: [4.6 Regression] ICE: SIGSEGV in walk_stmt_load_store_addr_ops (gimple.c:4894) with -O2 -fno-tree-dce Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Created attachment 22117 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22117 reduced testcase Compiler output: $ gcc -O2 -fno-tree-dce pr46130.c pr46130.c: In function 'foo': pr46130.c:15: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. Related valgrind output: ==22348== Invalid read of size 2 ==22348== at 0x6EA541: walk_stmt_load_store_addr_ops (gimple.c:4894) ==22348== by 0xAAB87A: rebuild_cgraph_edges (cgraphbuild.c:471) ==22348== by 0x796C5E: execute_one_pass (passes.c:1560) ==22348== by 0x796EF4: execute_pass_list (passes.c:1615) ==22348== by 0x79616B: do_per_function_toporder (passes.c:1153) ==22348== by 0x7973A5: execute_ipa_pass_list (passes.c:1932) ==22348== by 0xAB09D7: cgraph_optimize (cgraphunit.c:1696) ==22348== by 0xAB0B99: cgraph_finalize_compilation_unit (cgraphunit.c:1016) ==22348== by 0x4ABB8B: c_write_global_declarations (c-decl.c:9828) ==22348== by 0x88A553: toplev_main (toplev.c:931) ==22348== by 0x658ABBC: (below main) (in /lib64/libc-2.11.2.so) ==22348== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==22348== testcase.c: In function 'foo': testcase.c:15: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. Tested revisions: r165822 - crash r161659 - crash r159696 - OK 4.5 r165781 - OK
next reply other threads:[~2010-10-22 13:35 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-22 13:35 zsojka at seznam dot cz [this message] 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 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@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).