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/94630] General bug for changes needed to switch the powerpc64le-linux long double default Date: Wed, 25 Aug 2021 23:25:50 +0000 [thread overview] Message-ID: <bug-94630-4-JuhS1tpYQJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94630-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94630 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Michael Meissner <meissner@gcc.gnu.org>: https://gcc.gnu.org/g:4c5d76a655b9abdacaa992ab1167b33d35c3ffe9 commit r12-3151-g4c5d76a655b9abdacaa992ab1167b33d35c3ffe9 Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Aug 25 19:25:12 2021 -0400 Fix tests that require IBM 128-bit long double This patch adds 3 more selections to target-supports.exp to see if we can specify to use a particular long double format (IEEE 128-bit, IBM extended double, 64-bit), and the library support will track the changes for the long double. This is needed because two of the tests in the test suite use long double, and they are actually testing IBM extended double. This patch also forces the two tests that explicitly require long double to use the IBM double-double encoding to explicitly run the test. This requires GLIBC 2.32 or greater in order to do the switch. I have run tests on a little endian power9 system with 3 compilers. There were no regressions with these patches, and the two tests in the following patches now work if the default long double is not IBM 128-bit: * One compiler used the default IBM 128-bit format; * One compiler used the IEEE 128-bit format; (and) * One compiler used 64-bit long doubles. I have also tested compilers on a big endian power8 system with a compiler defaulting to power8 code generation and another with the default cpu set. There were no regressions. 2021-08-25 Michael Meissner <meissner@linux.ibm.com> gcc/testsuite/ PR target/94630 * gcc.target/powerpc/pr70117.c: Specify that we need the long double type to be IBM 128-bit. Remove the code to use __ibm128. * c-c++-common/dfp/convert-bfp-11.c: Specify that we need the long double type to be IBM 128-bit. Run the test at -O2 optimization. * lib/target-supports.exp (add_options_for_long_double_ibm128): New function. (check_effective_target_long_double_ibm128): New function. (add_options_for_long_double_ieee128): New function. (check_effective_target_long_double_ieee128): New function. (add_options_for_long_double_64bit): New function. (check_effective_target_long_double_64bit): New function.
next prev parent reply other threads:[~2021-08-25 23:25 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-17 2:07 [Bug target/94630] New: General bug for changes needed to switch the PowerPC " meissner at gcc dot gnu.org 2020-04-17 2:08 ` [Bug target/94630] " meissner at gcc dot gnu.org 2020-04-17 2:13 ` meissner at gcc dot gnu.org 2020-04-17 2:19 ` meissner at gcc dot gnu.org 2020-04-17 5:26 ` meissner at gcc dot gnu.org 2020-04-17 7:06 ` rguenth at gcc dot gnu.org 2020-04-17 12:40 ` meissner at gcc dot gnu.org 2020-04-17 15:53 ` segher at gcc dot gnu.org 2020-04-23 20:49 ` meissner at gcc dot gnu.org 2020-05-06 21:09 ` [Bug target/94630] General bug for changes needed to switch the powerpc64le-linux " murphyp at linux dot vnet.ibm.com 2021-08-25 23:25 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-03 17:05 ` cvs-commit at gcc dot gnu.org 2024-04-11 23:03 ` meissner 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-94630-4-JuhS1tpYQJ@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: linkBe 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).