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/104755] gcc.dg/vect/vect-bic-bitmask-10.c etc. FAIL
Date: Tue, 08 Mar 2022 11:33:57 +0000	[thread overview]
Message-ID: <bug-104755-4-EDXsD68xFW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104755-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:5f07095d22f58572c06997aa6d4f3bc456e1925d

commit r12-7533-g5f07095d22f58572c06997aa6d4f3bc456e1925d
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Tue Mar 8 11:32:59 2022 +0000

    vect: disable bitmask tests on sparc

    These testcases declare requiring vect_int which sparc declares as well
however
    sparc doesn't have an optab to vectorize comparisons so these testcases
fail to
    vectorize and so the tests fail.

    As such best coure of action is to just skip them on sparc as comparisons
are
    somewhat expected from a target that can do SIMD.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/104755
            * gcc.dg/vect/vect-bic-bitmask-10.c: Disable sparc.
            * gcc.dg/vect/vect-bic-bitmask-11.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-12.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-2.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-23.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-3.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-4.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-5.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-6.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-8.c: Likewise.
            * gcc.dg/vect/vect-bic-bitmask-9.c: Likewise.

  parent reply	other threads:[~2022-03-08 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 10:47 [Bug tree-optimization/104755] New: " ro at gcc dot gnu.org
2022-03-02 10:48 ` [Bug tree-optimization/104755] " ro at gcc dot gnu.org
2022-03-02 10:48 ` ro at gcc dot gnu.org
2022-03-02 12:34 ` tnfchris at gcc dot gnu.org
2022-03-02 12:43 ` ro at gcc dot gnu.org
2022-03-02 12:58 ` tnfchris at gcc dot gnu.org
2022-03-08 11:33 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-08 11:35 ` 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-104755-4-EDXsD68xFW@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).