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/108730] gcc.target/powerpc/bfp/scalar-test-neg-8.c fails on power 9 BE
Date: Wed, 08 Mar 2023 06:59:52 +0000	[thread overview]
Message-ID: <bug-108730-4-GXStwaPXpR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108730-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:9fd3d3567396e63cf5dde96ef03fcc92c6bcec71

commit r13-6541-g9fd3d3567396e63cf5dde96ef03fcc92c6bcec71
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Mar 8 00:56:32 2023 -0600

    testsuite: Adjust scalar-test-neg-8.c with lp64 [PR108730]

    The built-in function scalar_test_neg_qp is under stanza
    ieee128-hw, that is TARGET_FLOAT128_HW.  Since we don't
    have float128 hardware support on 32-bit as follows:

    if (TARGET_FLOAT128_HW && !TARGET_64BIT)
      {
        if ((rs6000_isa_flags_explicit & OPTION_MASK_FLOAT128_HW) != 0)
          error ("%qs requires %qs", "%<-mfloat128-hardware%>", "-m64");
        rs6000_isa_flags &= ~OPTION_MASK_FLOAT128_HW;
      }

    So adjust the case with lp64 effective target accordingly.

            PR testsuite/108730

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/bfp/scalar-test-neg-8.c: Adjust with lp64
            effective target requirement.

  parent reply	other threads:[~2023-03-08  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 21:21 [Bug target/108730] New: " seurer at gcc dot gnu.org
2023-02-24  6:24 ` [Bug testsuite/108730] " linkw at gcc dot gnu.org
2023-03-08  6:59 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-08  8:03 ` 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-108730-4-GXStwaPXpR@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).