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/work077)] Revert patch. Date: Mon, 31 Jan 2022 20:57:15 +0000 (GMT) [thread overview] Message-ID: <20220131205715.322B23857C46@sourceware.org> (raw) https://gcc.gnu.org/g:cb15f87ef42a151ff287489ff7da1218beddd0b3 commit cb15f87ef42a151ff287489ff7da1218beddd0b3 Author: Michael Meissner <meissner@linux.ibm.com> Date: Mon Jan 31 15:56:39 2022 -0500 Revert patch. 2022-01-26 Michael Meissner <meissner@the-meissners.org> gcc/ Revert patch. * config/rs6000/rs6000.cc (TARGET_IEEEQUAD_DEFAULT): If the compiler used to build the current compiler defaults to IEEE 128-bit long double, make that the default for this build. Diff: --- gcc/config/rs6000/rs6000.cc | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc index 3b4c496df56..666dec694a8 100644 --- a/gcc/config/rs6000/rs6000.cc +++ b/gcc/config/rs6000/rs6000.cc @@ -91,22 +91,14 @@ explicitly redefine TARGET_IEEEQUAD and TARGET_IEEEQUAD_DEFAULT to 0, so those systems will not pick up this default. This needs to be after all of the include files, so that POWERPC_LINUX and POWERPC_FREEBSD are - properly defined. - - If we are being built by a compiler that uses IEEE 128-bit as the default - long double and no explicit long double format was selected, then also - default long double to IEEE 128-bit. */ + properly defined. */ #ifndef TARGET_IEEEQUAD_DEFAULT #if !defined (POWERPC_LINUX) && !defined (POWERPC_FREEBSD) #define TARGET_IEEEQUAD_DEFAULT 1 #else -#ifdef __LONG_DOUBLE_IEEE128__ -#define TARGET_IEEEQUAD_DEFAULT 1 -#else #define TARGET_IEEEQUAD_DEFAULT 0 #endif #endif -#endif /* Don't enable PC-relative addressing if the target does not support it. */ #ifndef PCREL_SUPPORTED_BY_OS
next reply other threads:[~2022-01-31 20:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 20:57 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-02-03 0:47 Michael Meissner 2022-02-02 21:58 Michael Meissner 2022-02-02 18:47 Michael Meissner 2022-02-02 18:29 Michael Meissner 2022-02-02 4:58 Michael Meissner 2022-01-28 21:21 Michael Meissner 2022-01-28 14:53 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=20220131205715.322B23857C46@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: 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).