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/98602] Failure to optimise vector “x > -100 ? x : -100” to MAX_EXPR
Date: Mon, 11 Jan 2021 18:04:00 +0000	[thread overview]
Message-ID: <bug-98602-4-SvEIYNcZ8k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98602-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:

https://gcc.gnu.org/g:48c7f5b88116c894d76209db0f47216ed5ccd333

commit r11-6595-g48c7f5b88116c894d76209db0f47216ed5ccd333
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Mon Jan 11 18:03:21 2021 +0000

    aarch64: Add support for unpacked SVE mult, max and min

    This patch makes the SVE_INT_BINARY_IMM patterns support
    unpacked arithmetic, covering MUL, SMAX, SMIN, UMAX and UMIN.
    For min and max, the type suffix must be taken from the element
    size rather than the container size.

    The XFAILs are due to PR98602.

    gcc/
            * config/aarch64/aarch64-sve.md (<SVE_INT_BINARY_IMM:optab><mode>3)
            (@aarch64_pred_<SVE_INT_BINARY_IMM:optab><mode>)
            (*post_ra_<SVE_INT_BINARY_IMM:optab><mode>3): Extend from
SVE_FULL_I
            to SVE_I.

    gcc/testsuite/
            PR testsuite/98602
            * g++.target/aarch64/sve/max_1.C: New test.
            * g++.target/aarch64/sve/min_1.C: Likewise.
            * gcc.target/aarch64/sve/mul_2.c: Likewise.

  parent reply	other threads:[~2021-01-11 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 13:22 [Bug tree-optimization/98602] New: " rsandifo at gcc dot gnu.org
2021-01-08 13:48 ` [Bug tree-optimization/98602] " rguenth at gcc dot gnu.org
2021-01-11 18:04 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-29  6:38 ` pinskia at gcc dot gnu.org
2021-06-29  6:43 ` 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-98602-4-SvEIYNcZ8k@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).