From: MAHESH BODAPATI <bmahi496@linux.ibm.com>
To: libc-alpha@sourceware.org
Cc: rajis@linux.ibm.com, Mahesh Bodapati <mahesh.bodapati@ibm.com>
Subject: [PATCH] powerpc:GCC(<10) doesn't allow -mlong-double-64 after -mabi=ieeelongdouble
Date: Fri, 12 May 2023 05:22:59 -0500 [thread overview]
Message-ID: <20230512102259.2329923-1-bmahi496@linux.ibm.com> (raw)
From: Mahesh Bodapati <mahesh.bodapati@ibm.com>
Removed -mabi=ieeelongdouble on failing tests. It resolves the error.
error: ‘-mabi=ieeelongdouble’ requires ‘-mlong-double-128’
---
sysdeps/powerpc/powerpc64/le/Makefile | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/sysdeps/powerpc/powerpc64/le/Makefile b/sysdeps/powerpc/powerpc64/le/Makefile
index 53644d50cc..5214eb40ad 100644
--- a/sysdeps/powerpc/powerpc64/le/Makefile
+++ b/sysdeps/powerpc/powerpc64/le/Makefile
@@ -158,6 +158,23 @@ ifeq ($(subdir),stdio-common)
CFLAGS-printf_fp.c = $(type-float128-CFLAGS)
CFLAGS-printf_fphex.c = $(type-float128-CFLAGS)
CFLAGS-printf_size.c = $(type-float128-CFLAGS)
+#Older GCC (<10) doesn't like -mabi=ieeelongdouble and -mlong-double-64.
+$(foreach suf,$(all-object-suffixes),\
+ $(objpfx)tst-nldbl-scanf-binary-c11$(suf) \
+ $(objpfx)tst-nldbl-scanf-binary-c2x$(suf) \
+ $(objpfx)tst-nldbl-scanf-binary-gnu11$(suf) \
+ $(objpfx)tst-nldbl-scanf-binary-gnu89$(suf) \
+ ): sysdep-CFLAGS := $(filter-out -mabi=ieeelongdouble,$(sysdep-CFLAGS))
+endif
+
+#Older GCC (<10) doesn't like -mabi=ieeelongdouble and -mlong-double-64.
+ifeq ($(subdir), wcsmbs)
+$(foreach suf,$(all-object-suffixes),\
+ $(objpfx)tst-nldbl-wscanf-binary-c11$(suf) \
+ $(objpfx)tst-nldbl-wscanf-binary-c2x$(suf) \
+ $(objpfx)tst-nldbl-wscanf-binary-gnu11$(suf) \
+ $(objpfx)tst-nldbl-wscanf-binary-gnu89$(suf) \
+ ): sysdep-CFLAGS := $(filter-out -mabi=ieeelongdouble,$(sysdep-CFLAGS))
endif
# Disable linker noise on files using ieee128 long double internally
--
2.31.1
next reply other threads:[~2023-05-12 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 10:22 MAHESH BODAPATI [this message]
2023-05-15 13:09 ` Florian Weimer
2023-05-15 18:03 ` MAHESH BODAPATI
2023-05-15 19:26 ` Florian Weimer
2023-05-16 7:48 ` MAHESH BODAPATI
2023-05-17 22:08 ` Rajalakshmi Srinivasaraghavan
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=20230512102259.2329923-1-bmahi496@linux.ibm.com \
--to=bmahi496@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=mahesh.bodapati@ibm.com \
--cc=rajis@linux.ibm.com \
/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).