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 target/109697] arm: lack of MVE instruction costing causing worse codegen on a vec_duplicate
Date: Thu, 18 May 2023 10:01:00 +0000	[thread overview]
Message-ID: <bug-109697-4-MhWvqiFnlL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109697-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Stam Markianos-Wright
<stammark@gcc.gnu.org>:

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

commit r13-7351-gf9b84a16510c91af29add6cb1855306dfc8af035
Author: Stam Markianos-Wright <stam.markianos-wright@arm.com>
Date:   Thu Apr 27 15:54:16 2023 +0100

    arm testsuite: XFAIL or relax registers in some tests [PR109697]

    This is a simple testsuite tidy-up patch, addressing to types of errors:

    * The vcmp vector-scalar tests failing due to the compiler's preference
    of vector-vector comparisons, over vector-scalar comparisons. This is
    due to the lack of cost model for MVE and the compiler not knowing that
    the RTL vec_duplicate is free in those instructions. For now, we simply
    XFAIL these checks.
    * The tests for pr108177 had strict usage of q0 and r0 registers,
    meaning that they would FAIL with -mfloat-abi=softf. The register checks
    have now been relaxed. A couple of these run-tests also had incosistent
    use of integer MVE with floating point vectors, so I've now changed
    these to use FP MVE.

    gcc/testsuite/ChangeLog:
            PR target/109697
            * gcc.target/arm/mve/intrinsics/vcmpcsq_n_u16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpcsq_n_u32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpcsq_n_u8.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpeqq_n_f16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpeqq_n_f32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpeqq_n_u16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpeqq_n_u32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpeqq_n_u8.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpgeq_n_f16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpgeq_n_f32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpgtq_n_f16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpgtq_n_f32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmphiq_n_u16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmphiq_n_u32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmphiq_n_u8.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpleq_n_f16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpleq_n_f32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpltq_n_f16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpltq_n_f32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpneq_n_f16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpneq_n_f32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpneq_n_u16.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpneq_n_u32.c: XFAIL check.
            * gcc.target/arm/mve/intrinsics/vcmpneq_n_u8.c: XFAIL check.
            * gcc.target/arm/mve/pr108177-1.c: Relax registers.
            * gcc.target/arm/mve/pr108177-10.c: Relax registers.
            * gcc.target/arm/mve/pr108177-11.c: Relax registers.
            * gcc.target/arm/mve/pr108177-12.c: Relax registers.
            * gcc.target/arm/mve/pr108177-13.c: Relax registers.
            * gcc.target/arm/mve/pr108177-13-run.c: use mve_fp
            * gcc.target/arm/mve/pr108177-14.c: Relax registers.
            * gcc.target/arm/mve/pr108177-14-run.c: use mve_fp
            * gcc.target/arm/mve/pr108177-2.c: Relax registers.
            * gcc.target/arm/mve/pr108177-3.c: Relax registers.
            * gcc.target/arm/mve/pr108177-4.c: Relax registers.
            * gcc.target/arm/mve/pr108177-5.c: Relax registers.
            * gcc.target/arm/mve/pr108177-6.c: Relax registers.
            * gcc.target/arm/mve/pr108177-7.c: Relax registers.
            * gcc.target/arm/mve/pr108177-8.c: Relax registers.
            * gcc.target/arm/mve/pr108177-9.c: Relax registers.

  reply	other threads:[~2023-05-18 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 12:11 [Bug target/109697] New: " stammark at gcc dot gnu.org
2023-05-18 10:01 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-18 10:13 ` [Bug target/109697] " cvs-commit at gcc dot gnu.org
2023-05-18 10:44 ` cvs-commit 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-109697-4-MhWvqiFnlL@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).