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/105219] [12 Regression] SVE: Wrong code with -O3 -msve-vector-bits=128 -mtune=thunderx Date: Wed, 27 Apr 2022 12:30:19 +0000 [thread overview] Message-ID: <bug-105219-4-pHgYk0NQvj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105219-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105219 --- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Richard Biener from comment #16) > (In reply to rsandifo@gcc.gnu.org from comment #15) > > (In reply to Richard Biener from comment #14) > > > diff --git a/gcc/tree-vect-loop.cc b/gcc/tree-vect-loop.cc > > > index d7bc34636bd..3b63ab7b669 100644 > > > --- a/gcc/tree-vect-loop.cc > > > +++ b/gcc/tree-vect-loop.cc > > > @@ -9977,7 +9981,7 @@ vect_transform_loop (loop_vec_info loop_vinfo, gimple > > > *loop_vectorized_call) > > > lowest_vf) - 1 > > > : wi::udiv_floor (loop->nb_iterations_upper_bound + > > > bias_for_lowest, > > > lowest_vf) - 1); > > > - if (main_vinfo) > > > + if (main_vinfo && !main_vinfo->peeling_for_alignment) > > > { > > > unsigned int bound; > > > poly_uint64 main_iters > > It might be better to add the maximum peeling amount to main_iters. > > Maybe you'd prefer this anyway for GCC 12 though. > > > > I wonder if there's a similar problem for peeling for gaps, > > in cases where the epilogue doesn't need the same peeling. > > I don't quite understand the code in if (main_vinfo) but the point is > that for our case main_iters is zero (and so is prologue_iters if that > would exist). I'm not sure how the code can be adjusted with that > given it computes upper bounds and uses min() for the upper bound > of the epilogue - we'd need to adjust that with a max (2*vf-2, > old-upper-bound) > when there's prologue peeling and the short cut exists (I don't actually > compute that). That is, the code does if (can_div_away_from_zero_p (main_iters, LOOP_VINFO_VECT_FACTOR (loop_vinfo), &bound)) loop->nb_iterations_upper_bound = wi::umin ((widest_int) (bound - 1), loop->nb_iterations_upper_bound); and so assumes that the scalar epilogue never runs for more than epilogue VF - 1 times which is wrong. So I simply gated this whole code. But you are right that peeling for gaps would need similar handling so I'll play safe and add && !main_vinfo->peeling_for_gaps. > > peeling for gaps means we run the epilogue for main VF more iterations, > but that would just mean the vectorized epilogue executes one more time > and has peeling for gaps applied as well, so the scalar epilogue runs > for epilogue VF more iterations. > > I'm not sure what conditions prevent epilogue vectorization but I think > there were some at least.
next prev parent reply other threads:[~2022-04-27 12:30 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-11 13:29 [Bug target/105219] New: " acoplan at gcc dot gnu.org 2022-04-11 15:56 ` [Bug target/105219] " tnfchris at gcc dot gnu.org 2022-04-11 16:02 ` ktkachov at gcc dot gnu.org 2022-04-11 16:05 ` acoplan at gcc dot gnu.org 2022-04-11 16:12 ` tnfchris at gcc dot gnu.org 2022-04-12 11:08 ` tnfchris at gcc dot gnu.org 2022-04-12 11:30 ` rguenth at gcc dot gnu.org 2022-04-12 11:36 ` tnfchris at gcc dot gnu.org 2022-04-12 12:20 ` tnfchris at gcc dot gnu.org 2022-04-13 11:34 ` tnfchris at gcc dot gnu.org 2022-04-13 13:48 ` tnfchris at gcc dot gnu.org 2022-04-20 7:07 ` rguenth at gcc dot gnu.org 2022-04-25 7:07 ` tnfchris at gcc dot gnu.org 2022-04-27 11:56 ` [Bug tree-optimization/105219] " marxin at gcc dot gnu.org 2022-04-27 12:02 ` rguenth at gcc dot gnu.org 2022-04-27 12:06 ` rsandifo at gcc dot gnu.org 2022-04-27 12:27 ` rguenth at gcc dot gnu.org 2022-04-27 12:30 ` rguenth at gcc dot gnu.org [this message] 2022-04-27 13:44 ` avieira at gcc dot gnu.org 2022-04-28 8:10 ` cvs-commit at gcc dot gnu.org 2022-04-28 8:10 ` rguenth at gcc dot gnu.org 2022-04-28 12:17 ` rguenth at gcc dot gnu.org 2022-04-29 15:32 ` cvs-commit 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-105219-4-pHgYk0NQvj@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).