From: Paul E Murphy <murphyp@linux.ibm.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
"Paul E. Murphy" <murphyp@linux.vnet.ibm.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH v2 04/10] powerpc64le: Enforce -mabi=ibmlongdouble when -mfloat128 used
Date: Mon, 6 Apr 2020 11:49:29 -0500 [thread overview]
Message-ID: <bee88fd7-04fc-db6d-d792-8759fd71feda@linux.ibm.com> (raw)
In-Reply-To: <87a73smkpl.fsf@linux.ibm.com>
Pushed with patch 5, 8 and all requested changes. Thanks!
On 4/3/20 2:29 PM, Tulio Magno Quites Machado Filho wrote:
> "Paul E. Murphy via Libc-alpha" <libc-alpha@sourceware.org> writes:
>
>> I have observed a bug on 7.4.0 whereby __mulkc3 calls are
>> swapped with __multc3 depending on ABI selection. For the
>> sake of being overly cautious, build all _Float128 files
>> with ibm128 to workaround these compilers. This has been
>> noted in GCC BZ 84914, and will not be fixed for GCC 7.
>>
>> Likewise, non-math files built with _Float128 are assumed
>> to have ibm long double. Explicilty preserve this
>> assumption.
>>
>> Finally, add some bootstrapping code to avoid applying
>> these options until IEEE long double is enabled as they
>> require GCC 7 and above.
>
> Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
>
next prev parent reply other threads:[~2020-04-06 16:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 21:17 [PATCH v2 00/10] IEEE binary128 long double on powerpc64le Paul E. Murphy
2020-03-27 21:17 ` [PATCH v2 01/10] ldbl-128ibm-compat: workaround C++ redirect limitations Paul E. Murphy
2020-03-27 21:34 ` Joseph Myers
2020-04-01 20:29 ` Paul E Murphy
2020-04-01 20:41 ` DJ Delorie
2020-04-01 23:07 ` Joseph Myers
2020-04-02 16:48 ` Paul E Murphy
2020-03-27 21:17 ` [PATCH v2 02/10] ldbl-128ibm: simplify iscanonical.h Paul E. Murphy
2020-04-03 20:12 ` Tulio Magno Quites Machado Filho
2020-04-06 16:46 ` Paul E Murphy
2020-03-27 21:17 ` [PATCH v2 03/10] Rename __LONG_DOUBLE_USES_FLOAT128 to Paul E. Murphy
2020-04-03 19:22 ` Tulio Magno Quites Machado Filho
2020-03-27 21:17 ` [PATCH v2 04/10] powerpc64le: Enforce -mabi=ibmlongdouble when -mfloat128 used Paul E. Murphy
2020-04-03 19:29 ` Tulio Magno Quites Machado Filho
2020-04-06 16:49 ` Paul E Murphy [this message]
2020-03-27 21:17 ` [PATCH v2 05/10] powerpc64le: workaround ieee long double / _Float128 stdc++ bug Paul E. Murphy
2020-04-03 19:03 ` Tulio Magno Quites Machado Filho
2020-03-27 21:17 ` [PATCH v2 06/10] powerpc64le: raise GCC requirement to 7.3 for long double transition Paul E. Murphy
2020-03-31 20:47 ` Paul E Murphy
2020-03-27 21:17 ` [PATCH v2 07/10] powerpc64le: bump binutils version requirement to >= 2.26 Paul E. Murphy
2020-04-03 19:36 ` Tulio Magno Quites Machado Filho
2020-03-27 21:17 ` [PATCH v2 08/10] powerpc64le: enforce non-specific long double in .gnu.attributes section Paul E. Murphy
2020-04-03 19:49 ` Tulio Magno Quites Machado Filho
2020-03-27 21:18 ` [PATCH v2 09/10] powerpc64le: blacklist broken GCC compilers (e.g GCC 7.5.0) Paul E. Murphy
2020-04-03 20:38 ` Adhemerval Zanella
2020-04-07 19:57 ` Paul E Murphy
2020-03-27 21:18 ` [PATCH v2 10/10] powerpc64le: Enable support for IEEE long double Paul E. Murphy
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=bee88fd7-04fc-db6d-d792-8759fd71feda@linux.ibm.com \
--to=murphyp@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=murphyp@linux.vnet.ibm.com \
--cc=tuliom@ascii.art.br \
/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).