public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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: Wed, 19 Jan 2011 16:41:00 -0000 [thread overview] Message-ID: <bug-46130-4-uP1gplDr0Z@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-01-19 16:29:06 UTC --- Testcase that needs just -O2 -fno-tree-dce: static void foo (__builtin_va_list ap) { __builtin_va_arg (ap, char *)[0]; } int bar (__builtin_va_list ap) { foo (ap); foo (ap); } The issue is that I see nothing that checks the SSA_NAMEs in return_bb PHIs which originate from the split function are just in phi setting retval and nothing else. In this case because of -fno-tree-dce there is a dead PHI which the *.part.0 function doesn't pass through to the caller.
next prev parent reply other threads:[~2011-01-19 16:29 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 2011-01-19 16:41 ` jakub at gcc dot gnu.org [this message] 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-uP1gplDr0Z@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).