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 testsuite/108809] gcc.target/powerpc/builtins-5-p9-runnable.c fails on power 9 BE
Date: Mon, 17 Apr 2023 02:39:39 +0000	[thread overview]
Message-ID: <bug-108809-4-Mvz6YWPfgf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108809-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>:

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

commit r13-7202-ga1f25e04b8d10bbe5dcaf98bb7e17cdaec9f169d
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date:   Fri Apr 14 10:50:28 2023 +0800

    testsuite: update builtins-5-p9-runnable.c for BE

    Hi,

    As PR108809 mentioned, vec_xl_len_r and vec_xst_len_r are tested
    in gcc.target/powerpc/builtins-5-p9-runnable.c.
    The vector operand of these two bifs are different from the view
    of v16_int8 between BE and LE, even it is same from the view of
    128bits(uint128/V1TI).

    The test case gcc.target/powerpc/builtins-5-p9-runnable.c was
    written for LE environment, this patch updates it for BE.

    Tested on ppc64 BE and LE.
    Is this ok for trunk?

    BR,
    Jeff (Jiufu)

    gcc/testsuite/ChangeLog:

            PR testsuite/108809
            * gcc.target/powerpc/builtins-5-p9-runnable.c: Update for BE.

  parent reply	other threads:[~2023-04-17  2:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 21:57 [Bug target/108809] New: " seurer at gcc dot gnu.org
2023-03-09  7:35 ` [Bug target/108809] " linkw at gcc dot gnu.org
2023-04-13  9:43 ` guojiufu at gcc dot gnu.org
2023-04-13 12:43 ` guojiufu at gcc dot gnu.org
2023-04-17  2:39 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-09  7:37 ` [Bug testsuite/108809] " guojiufu 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-108809-4-Mvz6YWPfgf@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).