public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "irar at il dot ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/50412] gfortran -Ofast ICE in vect_do_peeling_for_loop_bound Date: Thu, 15 Sep 2011 11:42:00 -0000 [thread overview] Message-ID: <bug-50412-4-79IyyrJKGB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50412-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50412 Ira Rosen <irar at il dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |irar at il dot ibm.com AssignedTo|unassigned at gcc dot |irar at il dot ibm.com |gnu.org | --- Comment #2 from Ira Rosen <irar at il dot ibm.com> 2011-09-15 11:40:59 UTC --- The problem is that we don't support loop peeling for outer loops, but we support single element interleaving that may require peeling. I'll test this patch: Index: tree-vect-data-refs.c =================================================================== --- tree-vect-data-refs.c (revision 178780) +++ tree-vect-data-refs.c (working copy) @@ -2055,6 +2059,10 @@ vect_analyze_group_access (struct data_r HOST_WIDE_INT dr_step = TREE_INT_CST_LOW (step); HOST_WIDE_INT stride, last_accessed_element = 1; bool slp_impossible = false; + struct loop *loop = NULL; + + if (loop_vinfo) + loop = LOOP_VINFO_LOOP (loop_vinfo); /* For interleaving, STRIDE is STEP counted in elements, i.e., the size of the interleaving group (including gaps). */ @@ -2085,11 +2093,17 @@ vect_analyze_group_access (struct data_r if (loop_vinfo) { - LOOP_VINFO_PEELING_FOR_GAPS (loop_vinfo) = true; - if (vect_print_dump_info (REPORT_DETAILS)) fprintf (vect_dump, "Data access with gaps requires scalar " "epilogue loop"); + if (loop->inner) + { + if (vect_print_dump_info (REPORT_DETAILS)) + fprintf (vect_dump, "Peeling for outer loop is not supported"); + return false; + } + + LOOP_VINFO_PEELING_FOR_GAPS (loop_vinfo) = true; } return true; @@ -2272,10 +2286,17 @@ vect_analyze_group_access (struct data_r /* There is a gap in the end of the group. */ if (stride - last_accessed_element > 0 && loop_vinfo) { - LOOP_VINFO_PEELING_FOR_GAPS (loop_vinfo) = true; if (vect_print_dump_info (REPORT_DETAILS)) fprintf (vect_dump, "Data access with gaps requires scalar " "epilogue loop"); + if (loop->inner) + { + if (vect_print_dump_info (REPORT_DETAILS)) + fprintf (vect_dump, "Peeling for outer loop is not supported"); + return false; + } + + LOOP_VINFO_PEELING_FOR_GAPS (loop_vinfo) = true; } }
next prev parent reply other threads:[~2011-09-15 11:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-15 8:45 [Bug fortran/50412] New: " zeccav at gmail dot com 2011-09-15 10:07 ` [Bug tree-optimization/50412] " Joost.VandeVondele at pci dot uzh.ch 2011-09-15 11:42 ` irar at il dot ibm.com [this message] 2011-09-18 10:41 ` irar at gcc dot gnu.org 2011-09-25 9:27 ` [Bug tree-optimization/50412] [4.6/4.7 Regression] " irar at gcc dot gnu.org 2011-09-25 9:44 ` irar at il dot ibm.com
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-50412-4-79IyyrJKGB@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).