public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104579] vectorizer failed to reduce max & index search together
Date: Thu, 17 Feb 2022 08:14:09 +0000 [thread overview]
Message-ID: <bug-104579-4-43KQAh7XvP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104579-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104579
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #2)
> One possible way is sink maxInt = src[i] out of loop, when there's
> synchronised index search in the loop, just like below.
>
For scalar part, it's 1 conditional movement in loop vs. 1 load out of loop.
next prev parent reply other threads:[~2022-02-17 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 7:02 [Bug tree-optimization/104579] New: " crazylht at gmail dot com
2022-02-17 7:07 ` [Bug tree-optimization/104579] " crazylht at gmail dot com
2022-02-17 7:35 ` crazylht at gmail dot com
2022-02-17 8:14 ` crazylht at gmail dot com [this message]
2022-02-17 10:12 ` rguenth at gcc dot gnu.org
2022-02-17 11:15 ` crazylht at gmail dot com
2022-02-18 0:48 ` pinskia 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-104579-4-43KQAh7XvP@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).