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 middle-end/57661] [4.9 Regression] ICE: SIGSEGV in verify_ssa Date: Mon, 22 Jul 2013 22:03:00 -0000 [thread overview] Message-ID: <bug-57661-4-epoALx4EQf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57661-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57661 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yeah, ipa-split.c together with MEM_REF gimple_clobber_p and anonymous SSA_NAME cause this. ipa-split intentionally ignores clobber stmts during analysis, because they aren't real stmts, worst case we just ignore them and/or throw them away. If a clobber has a decl on lhs, then the decl is always present and not a problem. If it is a MEM_REF clobber with non-anonymous SSA_NAME, it is also just fine, ipa-split will during the cloning of the fn to *.part.* turn those SSA_NAMEs into SSA_NAME_IS_DEFAULT_DEF ones, and then tree-ssa-live will throw such clobbers away as useless. But anonymous SSA_NAMEs aren't meant to be ever SSA_NAME_IS_DEFAULT_DEF, which causes this problem. Perhaps ipa-split should just fix such SSA_NAMEs up (look up what anonymous SSA_NAMEs have no SSA_NAME_DEFAULT_STMT and remove all clobbers that depend on those and remove those SSA_NAMEs?
next prev parent reply other threads:[~2013-07-22 22:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-20 13:37 [Bug middle-end/57661] New: " zsojka at seznam dot cz 2013-06-24 11:09 ` [Bug middle-end/57661] " rguenth at gcc dot gnu.org 2013-07-12 1:50 ` mpolacek at gcc dot gnu.org 2013-07-22 22:03 ` jakub at gcc dot gnu.org [this message] 2013-07-22 22:36 ` jakub at gcc dot gnu.org 2013-07-22 23:50 ` jakub at gcc dot gnu.org 2013-08-13 19:58 ` 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-57661-4-epoALx4EQf@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).