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/102907] aarch64/shrn-combine-[123].c fail with SVE
Date: Mon, 25 Oct 2021 14:15:07 +0000	[thread overview]
Message-ID: <bug-102907-4-I2lCaFgxn7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102907-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:2cbfaba60661ebbdfcffe725ab55fbb323e2a187

commit r12-4663-g2cbfaba60661ebbdfcffe725ab55fbb323e2a187
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Mon Oct 25 15:14:04 2021 +0100

    AArch64 testsuite: Force shrn-combine-*.c to use NEON.

    These tests are testing Advanced SIMD codegen, so if the compiler or the
    testsuite is forcing SVE they will fail.

    This adds +nosve so that we always generate Advanced SIMD codegen.

    gcc/testsuite/ChangeLog:

            PR target/102907
            * gcc.target/aarch64/shrn-combine-1.c: Disable SVE.
            * gcc.target/aarch64/shrn-combine-2.c: Likewise.
            * gcc.target/aarch64/shrn-combine-3.c: Likewise.
            * gcc.target/aarch64/shrn-combine-4.c: Likewise.
            * gcc.target/aarch64/shrn-combine-5.c: Likewise.
            * gcc.target/aarch64/shrn-combine-6.c: Likewise.
            * gcc.target/aarch64/shrn-combine-7.c: Likewise.

  parent reply	other threads:[~2021-10-25 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 23:14 [Bug target/102907] New: " clyon at gcc dot gnu.org
2021-10-22 23:21 ` [Bug target/102907] " pinskia at gcc dot gnu.org
2021-10-25 14:15 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-25 14:16 ` tnfchris 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-102907-4-I2lCaFgxn7@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).