public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113078] [14 regression] reduction of cond_sub is not vectorized.
Date: Wed, 10 Jan 2024 14:26:55 +0000	[thread overview]
Message-ID: <bug-113078-4-HV60F5DKiK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113078-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:cac9d2d2346bf06b29b34e12cf0a005c37eacdc9

commit r14-7108-gcac9d2d2346bf06b29b34e12cf0a005c37eacdc9
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jan 10 14:13:25 2024 +0100

    tree-optimization/113078 - conditional subtraction reduction vectorization

    When if-conversion was changed to use .COND_ADD/SUB for conditional
    reduction it was forgotten to update reduction path handling to
    canonicalize .COND_SUB to .COND_ADD for vectorizable_reduction
    similar to what we do for MINUS_EXPR.  The following adds this
    and testcases exercising this at runtime and looking for the
    appropriate masked subtraction in the vectorized code on x86.

            PR tree-optimization/113078
            * tree-vect-loop.cc (check_reduction_path): Canonicalize
            .COND_SUB to .COND_ADD.

            * gcc.dg/vect/vect-reduc-cond-sub.c: New testcase.
            * gcc.target/i386/vect-pr113078.c: Likewise.

  parent reply	other threads:[~2024-01-10 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  3:53 [Bug tree-optimization/113078] New: " liuhongt at gcc dot gnu.org
2023-12-19  3:59 ` [Bug tree-optimization/113078] " pinskia at gcc dot gnu.org
2023-12-19  9:05 ` rguenth at gcc dot gnu.org
2024-01-10 14:26 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-10 14:27 ` 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-113078-4-HV60F5DKiK@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).