public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64493] [4.8/4.9/5 Regression] ICE at -O3 on x86_64-linux-gnu Date: Tue, 13 Jan 2015 12:22:00 -0000 [thread overview] Message-ID: <bug-64493-4-CqSQDeDsqR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64493-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64493 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- I tried to make a runtime testcase that tests for proper vectorization but all vectorized code ends up being dead. Nevertheless the following fixes the ICE: Index: gcc/tree-vect-loop.c =================================================================== --- gcc/tree-vect-loop.c (revision 219520) +++ gcc/tree-vect-loop.c (working copy) @@ -4580,7 +4580,10 @@ vect_finalize_reduction: && !STMT_VINFO_LIVE_P (exit_phi_vinfo)) || double_reduc); - STMT_VINFO_VEC_STMT (exit_phi_vinfo) = epilog_stmt; + if (double_reduc) + STMT_VINFO_VEC_STMT (exit_phi_vinfo) = inner_phi; + else + STMT_VINFO_VEC_STMT (exit_phi_vinfo) = epilog_stmt; if (!double_reduc || STMT_VINFO_DEF_TYPE (exit_phi_vinfo) != vect_double_reduction_def) and the generated code looks reasonable. I think we don't really support the case where the inner reduction result is used in the outer loop (but in !relevant stmts which end up dead). Well. Not 100% sure.
next prev parent reply other threads:[~2015-01-13 12:22 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-04 23:23 [Bug tree-optimization/64493] New: " su at cs dot ucdavis.edu 2015-01-05 8:57 ` [Bug tree-optimization/64493] [4.8/4.9/5 Regression] " jakub at gcc dot gnu.org 2015-01-13 11:42 ` rguenth at gcc dot gnu.org 2015-01-13 11:42 ` rguenth at gcc dot gnu.org 2015-01-13 12:22 ` rguenth at gcc dot gnu.org [this message] 2015-01-14 8:33 ` [Bug tree-optimization/64493] [4.8/4.9 " rguenth at gcc dot gnu.org 2015-01-14 8:33 ` [Bug tree-optimization/64493] [4.8/4.9/5 " rguenth at gcc dot gnu.org 2015-02-19 14:14 ` [Bug tree-optimization/64493] [4.8/4.9 " rguenth at gcc dot gnu.org 2015-02-24 14:27 ` [Bug tree-optimization/64493] [4.8 " rguenth at gcc dot gnu.org 2015-02-24 14:33 ` rguenth 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-64493-4-CqSQDeDsqR@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).