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/104208] -mlong-double-64 should override a previous -mabi=ibmlongdouble Date: Fri, 18 Mar 2022 19:10:20 +0000 [thread overview] Message-ID: <bug-104208-4-qUhXwTNskU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104208-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104208 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Peter Bergner <bergner@gcc.gnu.org>: https://gcc.gnu.org/g:51a34fdff2af99e2bb096436d6872c8ea434d177 commit r11-9668-g51a34fdff2af99e2bb096436d6872c8ea434d177 Author: Peter Bergner <bergner@linux.ibm.com> Date: Fri Mar 18 14:08:44 2022 -0500 rs6000: Allow -mlong-double-64 after -mabi={ibm,ieee}longdouble [PR104208, PR87496] The glibc build is showing a build error due to extra "error" checking from my PR87496 fix. That checking was overeager, disallowing setting the long double size to 64-bits if the 128-bit long double ABI had already been specified. Now we only emit an error if we specify a 128-bit long double ABI if our long double size is not 128 bits. This also fixes an erroneous error when -mabi=ieeelongdouble is used and ISA 2.06 is not enabled, but the long double size has been changed to 64 bits. 2022-03-04 Peter Bergner <bergner@linux.ibm.com> gcc/ PR target/87496 PR target/104208 * config/rs6000/rs6000.c (rs6000_option_override_internal): Make the ISA 2.06 requirement for -mabi=ieeelongdouble conditional on -mlong-double-128. Move the -mabi=ieeelongdouble and -mabi=ibmlongdouble error checking from here... * common/config/rs6000/rs6000-common.c (rs6000_handle_option): ... to here. gcc/testsuite/ PR target/87496 PR target/104208 * gcc.target/powerpc/pr104208-1.c: New test. * gcc.target/powerpc/pr104208-2.c: Likewise. * gcc.target/powerpc/pr87496-2.c: Swap long double options to trigger the expected error. * gcc.target/powerpc/pr87496-3.c: Likewise. (cherry picked from commit cb16bc3b5f34733ef9bbf8d2e3acacdecb099a62)
next prev parent reply other threads:[~2022-03-18 19:10 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 18:30 [Bug target/104208] New: " fw at gcc dot gnu.org 2022-01-24 18:30 ` [Bug target/104208] " fw at gcc dot gnu.org 2022-02-28 20:08 ` segher at gcc dot gnu.org 2022-03-01 22:55 ` bergner at gcc dot gnu.org 2022-03-01 23:16 ` jakub at gcc dot gnu.org 2022-03-02 0:37 ` bergner at gcc dot gnu.org 2022-03-02 8:23 ` jakub at gcc dot gnu.org 2022-03-02 17:56 ` bergner at gcc dot gnu.org 2022-03-02 18:08 ` fw at gcc dot gnu.org 2022-03-04 6:16 ` bergner at gcc dot gnu.org 2022-03-04 15:04 ` cvs-commit at gcc dot gnu.org 2022-03-04 23:43 ` bergner at gcc dot gnu.org 2022-03-05 2:11 ` bergner at gcc dot gnu.org 2022-03-11 11:35 ` fw at gcc dot gnu.org 2022-03-18 19:10 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-18 19:10 ` cvs-commit at gcc dot gnu.org 2022-03-18 19:21 ` bergner 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-104208-4-qUhXwTNskU@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).