public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/meissner/heads/work085)] Disable float128 tests on VxWorks.
Date: Wed,  6 Apr 2022 22:52:35 +0000 (GMT)	[thread overview]
Message-ID: <20220406225235.16A8E3858D37@sourceware.org> (raw)

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

commit c8dddce847649ec8ff180691c10be63605d88028
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Apr 6 18:52:16 2022 -0400

    Disable float128 tests on VxWorks.
    
    In PR target/104253, it was pointed out the that test case added as part
    of fixing the PR does not work on VxWorks because float128 is not
    supported on that system.  I have modified the three tests for float128 so
    that they are manually excluded on VxWorks systems.  In looking at the
    code, I also added checks in check_effective_target_ppc_ieee128_ok to
    disable the systems that will never support VSX instructions which are
    required for float128 support (eabi, eabispe, darwin).
    
    2022-04-06   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/testsuite/
            PR target/104253
            * lib/target-supports.exp (check_ppc_float128_sw_available): Do
            not run float128 tests on VxWorks.
            (check_ppc_float128_hw_available): Likewise.
            (check_effective_target_ppc_ieee128_ok): Do not run float128 tests
            on VxWorks.  Also disable systems that do not support VSX
            instructions.

Diff:
---
 gcc/testsuite/lib/target-supports.exp | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index ff8edbd3e17..a4142eaee27 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -2318,10 +2318,12 @@ proc check_ppc_mma_hw_available { } {
 proc check_ppc_float128_sw_available { } {
     return [check_cached_effective_target ppc_float128_sw_available {
 	# Some simulators are known to not support VSX/power8/power9
-	# instructions.	For now, disable on Darwin.
+	# instructions. For now, disable on Darwin.  Disable on VxWorks as
+	# well.
 	if { [istarget powerpc-*-eabi]
 	     || [istarget powerpc*-*-eabispe]
-	     || [istarget *-*-darwin*]} {
+	     || [istarget *-*-darwin*]
+	     || [istarget *-*-vxworks]} {
 	    expr 0
 	} else {
 	    set options "-mfloat128 -mvsx"
@@ -2344,10 +2346,11 @@ proc check_ppc_float128_sw_available { } {
 proc check_ppc_float128_hw_available { } {
     return [check_cached_effective_target ppc_float128_hw_available {
 	# Some simulators are known to not support VSX/power8/power9
-	# instructions.	For now, disable on Darwin.
+	# instructions.	For now, disable on Darwin and VxWorks.
 	if { [istarget powerpc-*-eabi]
 	     || [istarget powerpc*-*-eabispe]
-	     || [istarget *-*-darwin*]} {
+	     || [istarget *-*-darwin*]
+	     || [istarget *-*-vxworks]} {
 	    expr 0
 	} else {
 	    set options "-mfloat128 -mvsx -mfloat128-hardware -mpower9-vector"
@@ -2370,8 +2373,12 @@ proc check_ppc_float128_hw_available { } {
 # See if the __ieee128 keyword is understood.
 proc check_effective_target_ppc_ieee128_ok { } {
     return [check_cached_effective_target ppc_ieee128_ok {
-	# disable on AIX.
-	if { [istarget *-*-aix*] } {
+	# disable on AIX, Darwin, VxWorks and targets that don't support VSX.
+	if { [istarget *-*-aix*]
+	     || [istarget powerpc-*-eabi]
+	     || [istarget powerpc*-*-eabispe]
+	     || [istarget *-*-darwin*]
+	     || [istarget *-*-vxworks]} {
 	    expr 0
 	} else {
 	    set options "-mfloat128"


                 reply	other threads:[~2022-04-06 22:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220406225235.16A8E3858D37@sourceware.org \
    --to=meissner@gcc.gnu.org \
    --cc=gcc-cvs@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).