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/108758] [12/13 Regression] gcc.target/powerpc/float128-cmp2-runnable.c fails with excess errors on power 9 BE since r12-5752
Date: Tue, 09 May 2023 08:29:35 +0000	[thread overview]
Message-ID: <bug-108758-4-uSyXkCtxLX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108758-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:6bc2cf17eb9e79e69498f721cb42c59c3eda69fc

commit r13-7309-g6bc2cf17eb9e79e69498f721cb42c59c3eda69fc
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Apr 26 00:21:14 2023 -0500

    rs6000: Guard power9-vector for vsx_scalar_cmp_exp_qp_* [PR108758]

    __builtin_vsx_scalar_cmp_exp_qp_{eq,gt,lt,unordered} used
    to be guarded with condition TARGET_P9_VECTOR before new
    bif framework was introduced (r12-5752-gd08236359eb229),
    since r12-5752 they are placed under stanza ieee128-hw,
    that is to check condition TARGET_FLOAT128_HW, it caused
    test case float128-cmp2-runnable.c to fail at -m32 as the
    condition TARGET_FLOAT128_HW isn't satisified with -m32.

    By checking the commit history, I didn't see any notes on
    why this condition change on them was made, so this patch
    is to move these bifs from stanza ieee128-hw to stanza
    power9-vector as before.

            PR target/108758

    gcc/ChangeLog:

            * config/rs6000/rs6000-builtins.def
            (__builtin_vsx_scalar_cmp_exp_qp_eq,
__builtin_vsx_scalar_cmp_exp_qp_gt
            __builtin_vsx_scalar_cmp_exp_qp_lt,
            __builtin_vsx_scalar_cmp_exp_qp_unordered): Move from stanza
ieee128-hw
            to power9-vector.

    (cherry picked from commit 33a44e3aa81f9fdf8f6b87018abd4c664e545b53)

  parent reply	other threads:[~2023-05-09  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 23:06 [Bug target/108758] New: gcc.target/powerpc/float128-cmp2-runnable.c fails with excess errors on power 9 BE seurer at gcc dot gnu.org
2023-04-26  5:22 ` [Bug target/108758] " cvs-commit at gcc dot gnu.org
2023-04-26  5:25 ` [Bug target/108758] [12/13 Regression] gcc.target/powerpc/float128-cmp2-runnable.c fails with excess errors on power 9 BE since r12-5752 linkw at gcc dot gnu.org
2023-04-27 11:30 ` rguenth at gcc dot gnu.org
2023-05-08 12:26 ` rguenth at gcc dot gnu.org
2023-05-09  5:18 ` cvs-commit at gcc dot gnu.org
2023-05-09  8:29 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-09  8:34 ` linkw 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-108758-4-uSyXkCtxLX@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).