public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul E Murphy <murphyp@linux.ibm.com>
To: Florian Weimer <fw@deneb.enyo.de>,
	"Paul E. Murphy via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3 3/6] powerpc64le: raise GCC requirement to 7.4 for long double transition
Date: Wed, 22 Apr 2020 14:33:50 -0500	[thread overview]
Message-ID: <e03d764f-e3d6-c915-de52-411cdf9837e7@linux.ibm.com> (raw)
In-Reply-To: <87lfmnim4v.fsf@mid.deneb.enyo.de>



On 4/22/20 10:19 AM, Florian Weimer wrote:
> * Paul E. Murphy via Libc-alpha:
> 
>> diff --git a/manual/install.texi b/manual/install.texi
>> index 71bf47cac6..66de8ea59b 100644
>> --- a/manual/install.texi
>> +++ b/manual/install.texi
>> @@ -507,6 +507,11 @@ the newest version of the compiler that is known to work for building
>>   release time, GCC 9.2.1 is the newest compiler verified to work to build
>>   @theglibc{}.
>>   
>> +For PowerPC 64-bits little-endian (powerpc64le), a GCC version with
>> +support for @option{-mno-gnu-attribute} is required.  As of release time,
>> +this means GCC 7.4 (excepting 7.5) or newer. The compiler option is required
>> +for building the GNU C Library with support for IEEE long double.
> 
> Why “excepting 7.5”?  Somewhere, there should be an explanation, maybe
> in a @c comment in the Texinfo sources if it's too confusing to end
> users.

FSF GCC 7.5 does not accept both the -mabi=* and -mlong-double-128 
options being present on the command line.  Ironically, it errors 
instructing you to pass the -mlong-double-128 option.

> Also, missing two spaces at the end of sentences.
> 
> And quick question for my understanding: Could we get the effect of
> -mno-gnu-attribute using strip if we wanted?  (Not that I think this
> change is required, I'm fine with bumping the minimum GCC
> requirement.)

Yes, I think one could post-process each object file to strip the 
.gnu.attributes section.  Though, you do highlight an impedance mismatch 
between the commit message and documentation regarding the -mabi 
requirements.

How about the following instead?

For PowerPC 64-bits little-endian (powerpc64le), a GCC version with 
support for @option{-mno-gnu-attribute}, @option{-mabi=ieeelongdouble}, 
and @option{-mabi=ibmlondouble} is required.  Likewise, the compiler 
must also support passing @options{-mlong-double-128} with the preceding 
options.  As of release, this implies GCC 7.4 and newer (excepting GCC 
7.5.0, see GCC PR94200).  These additional features are required for 
building the GNU C Library with support for IEEE long double.

  reply	other threads:[~2020-04-22 19:33 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 [this message]
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
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=e03d764f-e3d6-c915-de52-411cdf9837e7@linux.ibm.com \
    --to=murphyp@linux.ibm.com \
    --cc=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).