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)] Update ChangeLog.meissner.
Date: Wed,  6 Apr 2022 22:54:24 +0000 (GMT)	[thread overview]
Message-ID: <20220406225424.4D0AE3858D37@sourceware.org> (raw)

https://gcc.gnu.org/g:891cf99f6a4007f2851ca4eb5f7e56edd5d9cc1e

commit 891cf99f6a4007f2851ca4eb5f7e56edd5d9cc1e
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Apr 6 18:54:05 2022 -0400

    Update ChangeLog.meissner.
    
    2022-04-06   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
            * ChangeLog.meissner: Update.

Diff:
---
 gcc/ChangeLog.meissner | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 3e96d3f36c8..4e39b994616 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,28 @@
+==================== Work086, patch #1:
+
+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.
+
+==================== Work086, branch head:
+
 2022-04-06   Michael Meissner  <meissner@linux.ibm.com>
 
 	Clone branch


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 22:54 Michael Meissner [this message]
2022-04-07 20:24 Michael Meissner
2022-04-07 22:24 Michael Meissner
2022-04-11 18:04 Michael Meissner
2022-04-11 18:14 Michael Meissner
2022-04-12 18:47 Michael Meissner
2022-04-14 20:19 Michael Meissner

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=20220406225424.4D0AE3858D37@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).