From: Florian Weimer <fw@deneb.enyo.de>
To: "Paul E. Murphy via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3 5/6] powerpc64le: blacklist broken GCC compilers (e.g GCC 7.5.0)
Date: Wed, 22 Apr 2020 17:23:26 +0200 [thread overview]
Message-ID: <87d07zilxt.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <b1b017ef826bcd891b73598c92e2a1b6105f8ca5.1586199342.git.murphyp@linux.vnet.ibm.com> (Paul E. Murphy via Libc-alpha's message of "Mon, 6 Apr 2020 14:12:38 -0500")
* Paul E. Murphy via Libc-alpha:
> GCC 7.5.0 (BZ# 94200) will refuse to compile if both -mabi=% and
> -mlong-double-128 are passed on the command line. Surprisingly,
> it will work happily if the latter is not. For the sake of
> maintianing status quo, test for and blacklist such compilers.
GCC PR reference syntax (as mentioned before), and typo: maintianing
> diff --git a/sysdeps/powerpc/powerpc64/le/configure.ac b/sysdeps/powerpc/powerpc64/le/configure.ac
> index 630086bd88..dde956505c 100644
> --- a/sysdeps/powerpc/powerpc64/le/configure.ac
> +++ b/sysdeps/powerpc/powerpc64/le/configure.ac
> @@ -51,6 +51,21 @@ CFLAGS="$save_CFLAGS"])
> AS_IF([test "$libc_cv_compiler_powerpc64le_ice" != "yes"],
> [critic_missing="$critic_missing __builtin_signbit is broken. GCC 7.4 or newer is required to resolve (BZ 83862)."])
>
> +dnl Some old compiler versions give out error messages when combining
> +dnl -mabi=% and -mlong-double-128. i.e GCC 7.5.0 (BZ# 94200)
PR reference.
> +AC_CACHE_CHECK([if $CC compiles with -mabi=ieeelongdouble and -mlong-double-128],
> + libc_cv_compiler_powerpc64le_ldbl128_mabi, [dnl
> +save_CFLAGS="$CFLAGS"
> +CFLAGS="$CFLAGS -mabi=ieeelongdouble -mlong-double-128"
> +AC_COMPILE_IFELSE([AC_LANG_SOURCE([[
> +long double x;
> +]])],
> + [libc_cv_compiler_powerpc64le_ldbl128_mabi=yes],
> + [libc_cv_compiler_powerpc64le_ldbl128_mabi=no])
> +CFLAGS="$save_CFLAGS"])
> +AS_IF([test "$libc_cv_compiler_powerpc64le_ldbl128_mabi" == "no"],
> + [critic_missing="$critic_missing The compiler must support -mabi=ieeelongdouble and -mlongdouble simultaneously."])
> +
> # Binutils (objcopy) 2.26 or newer required to support the --update-section
> # feature for fixing up .gnu.attribute section with IEEE ldbl.
> AC_CHECK_PROG_VER(OBJCOPY, $OBJCOPY, --version,
This change looks reasonable to me.
Maybe add the @c comment to the install.texi file with this patch?
Something like this:
@c See this autoconf check:
@c if $CC compiles with -mabi=ieeelongdouble and -mlong-double-128
next prev parent reply other threads:[~2020-04-22 15:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 19:12 [PATCH v3 0/6] IEEE binary128 long double on powerpc64le Paul E. Murphy
2020-04-06 19:12 ` [PATCH v3 1/6] ldbl-128ibm-compat: workaround GCC 9 C++ BZ 90731 Paul E. Murphy
2020-04-15 14:20 ` Paul E Murphy
2020-04-22 14:58 ` Paul E Murphy
2020-04-22 15:11 ` Florian Weimer
2020-04-22 21:17 ` Paul E Murphy
2020-04-23 5:48 ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 2/6] Rename __LONG_DOUBLE_USES_FLOAT128 to __LDOUBLE_REDIRECTS_TO_FLOAT128_ABI Paul E. Murphy
2020-04-15 14:21 ` Paul E Murphy
2020-04-22 14:59 ` Paul E Murphy
2020-04-06 19:12 ` [PATCH v3 3/6] powerpc64le: raise GCC requirement to 7.4 for long double transition Paul E. Murphy
2020-04-22 15:19 ` Florian Weimer
2020-04-22 19:33 ` Paul E Murphy
2020-04-06 19:12 ` [PATCH v3 4/6] powerpc64le: bump binutils version requirement to >= 2.26 Paul E. Murphy
2020-04-22 15:20 ` Florian Weimer
2020-04-06 19:12 ` [PATCH v3 5/6] powerpc64le: blacklist broken GCC compilers (e.g GCC 7.5.0) Paul E. Murphy
2020-04-22 15:23 ` Florian Weimer [this message]
2020-04-06 19:12 ` [PATCH v3 6/6] powerpc64le: Enable support for IEEE long double Paul E. Murphy
2020-04-22 15:03 ` Paul E Murphy
2020-04-22 15:15 ` Florian Weimer
2020-04-22 16:20 ` Paul E Murphy
2020-04-22 16:23 ` Florian Weimer
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=87d07zilxt.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.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).