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 target/102404] Loop vectorized with 32 byte vectors actually uses 16 byte vectors
Date: Wed, 22 Sep 2021 02:37:55 +0000	[thread overview]
Message-ID: <bug-102404-4-Bp3Tp8ZNew@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102404-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102404

--- Comment #5 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Freddie Witherden from comment #4)
> Created attachment 51485 [details]
> Clang assembly.

It seems to be because the current GCC loop vectorizer does not support
different vector sizes, and here the index vector is 256bit. Change tripcount
to 16 successfully generate zmm.

  parent reply	other threads:[~2021-09-22  2:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 22:17 [Bug tree-optimization/102404] New: " freddie at witherden dot org
2021-09-18 22:18 ` [Bug tree-optimization/102404] " freddie at witherden dot org
2021-09-20  9:04 ` [Bug target/102404] " rguenth at gcc dot gnu.org
2021-09-20 12:16 ` freddie at witherden dot org
2021-09-20 12:17 ` freddie at witherden dot org
2021-09-22  2:37 ` crazylht at gmail dot com [this message]
2021-09-22  2:40 ` crazylht at gmail 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-102404-4-Bp3Tp8ZNew@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).