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/109048] [13 regression] redundant mask compare generated by vectorizer.
Date: Thu, 13 Apr 2023 07:30:58 +0000	[thread overview]
Message-ID: <bug-109048-4-k6UUjDLIY5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109048-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
The recent patch improved this to avoid some of the compares.  We still have
the three-argument PHI and thus three VEC_CONDs.

.L10:
        vmovups (%rdi,%rdx), %ymm0
        vcmpltps        %ymm6, %ymm0, %ymm3
        vcmpltps        %ymm2, %ymm0, %ymm1
        vpandn  %ymm1, %ymm3, %ymm1
        vblendvps       %ymm1, %ymm5, %ymm4, %ymm1
        vblendvps       %ymm3, %ymm7, %ymm1, %ymm1
        vaddps  %ymm1, %ymm0, %ymm0
        vaddps  (%rax,%rdx), %ymm0, %ymm0
        vmovups %ymm0, (%rax,%rdx)
        addq    $32, %rdx
        cmpq    $1024, %rdx
        jne     .L10

vs. GCC 12

.L6:
        vmovups (%rdi,%rdx), %ymm1
        vcmpltps        %ymm5, %ymm1, %ymm0
        vcmpltps        %ymm6, %ymm1, %ymm4
        vblendvps       %ymm0, %ymm3, %ymm2, %ymm0
        vandps  %ymm3, %ymm4, %ymm4
        vaddps  %ymm4, %ymm0, %ymm0
        vaddps  %ymm1, %ymm0, %ymm0
        vaddps  (%rax,%rdx), %ymm0, %ymm0
        vmovups %ymm0, (%rax,%rdx)
        addq    $32, %rdx
        cmpq    $1024, %rdx
        jne     .L6

which at least overall looks comparable.

  parent reply	other threads:[~2023-04-13  7:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  6:01 [Bug tree-optimization/109048] New: " crazylht at gmail dot com
2023-03-07  6:03 ` [Bug tree-optimization/109048] " crazylht at gmail dot com
2023-03-07  6:13 ` crazylht at gmail dot com
2023-03-07  6:22 ` crazylht at gmail dot com
2023-03-07  6:34 ` crazylht at gmail dot com
2023-03-07  9:17 ` rguenth at gcc dot gnu.org
2023-03-07  9:38 ` jakub at gcc dot gnu.org
2023-03-07 10:09 ` rguenther at suse dot de
2023-03-27  8:26 ` rguenth at gcc dot gnu.org
2023-03-27  9:18 ` rguenth at gcc dot gnu.org
2023-03-27 10:37 ` rguenth at gcc dot gnu.org
2023-03-28 12:20 ` rguenth at gcc dot gnu.org
2023-04-13  7:30 ` rguenth at gcc dot gnu.org [this message]
2023-04-13  8:14 ` 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-109048-4-k6UUjDLIY5@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).