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/101668] BB vectorizer doesn't handle lowpart of existing vector
Date: Wed, 25 May 2022 13:05:01 +0000	[thread overview]
Message-ID: <bug-101668-4-OwXM5hYLLG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101668-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 53031
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53031&action=edit
patch

This works now - the support for enhanced vec_perm_const is still not complete
on trunk (it claims all is OK ...) so it will ICE for testcases that would
require this.  But lowpart extracts and concats (untested) should work.

I'll extend coverage once the dependences are on trunk.  For the testcase at
hand
we now generate

bar_s32_s64:
.LFB0:
        .cfi_startproc
        vpmovsxdq       %ymm0, %zmm0
        vmovdqa64       %zmm0, (%rdi)
        ret

with AVX512.

  parent reply	other threads:[~2022-05-25 13:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  1:47 [Bug tree-optimization/101668] New: vectorizer doesn't categorize vector construct cost right crazylht at gmail dot com
2021-07-29  6:55 ` [Bug tree-optimization/101668] BB vectorizer doesn't handle lowpart of existing vector rguenth at gcc dot gnu.org
2021-07-29  7:03 ` crazylht at gmail dot com
2022-05-20  9:03 ` rguenth at gcc dot gnu.org
2022-05-20  9:13 ` crazylht at gmail dot com
2022-05-20  9:25 ` rguenth at gcc dot gnu.org
2022-05-25 13:05 ` rguenth at gcc dot gnu.org [this message]
2022-06-02  6:46 ` cvs-commit at gcc dot gnu.org
2022-06-02  6:47 ` rguenth 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-101668-4-OwXM5hYLLG@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).