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/110474] Vect: the epilog vect loop should have small VF if the loop is unrolled during vectorization
Date: Thu, 29 Jun 2023 07:33:24 +0000 [thread overview]
Message-ID: <bug-110474-4-30bohLlngD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110474-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110474
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think it's reasonable to not apply unrolling to the vectorized epilogue, but
note we have to be careful to adjust the maximum number of iterations for it we
compute. Note this will also necessarily make the vectorized epilogue iterate.
We could also leave the decision to the target, providing a
suggested_epilog_"unroll" factor. That could also be used to for example
get a 128bit vector epilogue for a 512bit main loop to address similar
concerns there.
next prev parent reply other threads:[~2023-06-29 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 4:35 [Bug tree-optimization/110474] New: " hliu at amperecomputing dot com
2023-06-29 7:33 ` rguenth at gcc dot gnu.org [this message]
2023-07-06 2:07 ` [Bug tree-optimization/110474] " cvs-commit at gcc dot gnu.org
2023-07-06 2:21 ` hliu at amperecomputing dot 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-110474-4-30bohLlngD@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: link
Be 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).