Jonathan Wakely writes:
>>Hmm, yes, you pointed me to __frexpieee128 a few months ago, but for
>>some reason I either didn't switch to using it, or lost a patch when
>>squashing and rebasing branches. Hopefully I just forgot to change it,
>>but I'll double check to make sure I haven't left any
On 10/12/20 11:14 -0600, Peter Bergner via Libstdc++ wrote:
On 12/10/20 10:14 AM, Jonathan Wakely wrote:
On 04/12/20 00:35 +, Jonathan Wakely wrote:
On 03/12/20 20:07 -0300, Tulio Magno Quites Machado Filho via Libstdc++ wrote:
I suggest to replace frexpf128 with __frexpieee128.
The
On 12/10/20 10:14 AM, Jonathan Wakely wrote:
> On 04/12/20 00:35 +, Jonathan Wakely wrote:
>> On 03/12/20 20:07 -0300, Tulio Magno Quites Machado Filho via Libstdc++
>> wrote:
>>> I suggest to replace frexpf128 with __frexpieee128.
>>>
>>> The former is available on a glibc that support
On 04/12/20 00:35 +, Jonathan Wakely wrote:
On 03/12/20 20:07 -0300, Tulio Magno Quites Machado Filho via Libstdc++ wrote:
Jonathan Wakely via Libstdc++ writes:
diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac
index cbfdf4c6bad..d25842fef35 100644
---
On 03/12/20 20:07 -0300, Tulio Magno Quites Machado Filho via Libstdc++ wrote:
Jonathan Wakely via Libstdc++ writes:
diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac
index cbfdf4c6bad..d25842fef35 100644
--- a/libstdc++-v3/configure.ac
+++ b/libstdc++-v3/configure.ac
@@
Jonathan Wakely via Libstdc++ writes:
> diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac
> index cbfdf4c6bad..d25842fef35 100644
> --- a/libstdc++-v3/configure.ac
> +++ b/libstdc++-v3/configure.ac
> @@ -421,12 +425,43 @@ case "$target" in
>
>
On Tue, Dec 01, 2020 at 10:36:10PM +, Jonathan Wakely wrote:
> I've attached a complete patch including those generated files, and
> I've also pushed the branch to refs/users/redi/heads/ieee128-squash in
> the gcc.gnu.org Git repo. That branch includes your patch for PR
> libgcc/97543 which is
Note this is just to keep the gcc-patches archive up to date. I originally
posted this reply but the attached config.log file was too big. It was also
sent directly to Jonathan, and he replied. So I canceled the gcc-patches post,
and I'm sending out this one with a bzip2's config.log:
On Tue,
On Tue, Dec 01, 2020 at 10:36:10PM +, Jonathan Wakely wrote:
> You need to run autoconf-2.69's autoreconf in the libstdc++-v3 source
> tree to regenerate configure, Makefile.in etc. Without doing that
> you're just running the same configure script as is on current trunk,
> and that doesn't
On Tue, 1 Dec 2020 at 22:25, Michael Meissner wrote:
>
> On Tue, Dec 01, 2020 at 09:10:30PM +, Jonathan Wakely wrote:
> > On Tue, 1 Dec 2020 at 19:13, Michael Meissner via Libstdc++
> > wrote:
> > >
> > > On Tue, Dec 01, 2020 at 04:04:30PM +, Jonathan Wakely wrote:
> > > > On 01/12/20
On Tue, 1 Dec 2020 at 21:10, Jonathan Wakely wrote:
>
> On Tue, 1 Dec 2020 at 19:13, Michael Meissner via Libstdc++
> wrote:
> >
> > On Tue, Dec 01, 2020 at 04:04:30PM +, Jonathan Wakely wrote:
> > > On 01/12/20 15:10 +, Jonathan Wakely wrote:
> > > >On 30/11/20 16:30 -0500, Michael
On Tue, 1 Dec 2020 at 19:13, Michael Meissner via Libstdc++
wrote:
>
> On Tue, Dec 01, 2020 at 04:04:30PM +, Jonathan Wakely wrote:
> > On 01/12/20 15:10 +, Jonathan Wakely wrote:
> > >On 30/11/20 16:30 -0500, Michael Meissner via Libstdc++ wrote:
> > >>Jonathan, could you send a fresh
On Tue, Dec 01, 2020 at 04:04:30PM +, Jonathan Wakely wrote:
> On 01/12/20 15:10 +, Jonathan Wakely wrote:
> >On 30/11/20 16:30 -0500, Michael Meissner via Libstdc++ wrote:
> >>Jonathan, could you send a fresh set of patches (or at least replacements)?
> >> I
> >>tried installing the
On 01/12/20 15:10 +, Jonathan Wakely wrote:
On 30/11/20 16:30 -0500, Michael Meissner via Libstdc++ wrote:
Jonathan, could you send a fresh set of patches (or at least replacements)? I
tried installing the patches on a master branch I checked out this morning, and
I got two rejects:
I
On 30/11/20 16:30 -0500, Michael Meissner via Libstdc++ wrote:
Jonathan, could you send a fresh set of patches (or at least replacements)? I
tried installing the patches on a master branch I checked out this morning, and
I got two rejects:
I don't understand why those chunks failed, but I'll
On 30/11/20 17:29 -0600, Segher Boessenkool wrote:
Hi!
Thank you for all this.
On Wed, Nov 11, 2020 at 09:50:01PM +, Jonathan Wakely wrote:
This adds support for the new __ieee128 long double format on
powerpc64le targets.
* testsuite/27_numerics/complex/abi_tag.cc: Add
Hi!
Thank you for all this.
On Wed, Nov 11, 2020 at 09:50:01PM +, Jonathan Wakely wrote:
> This adds support for the new __ieee128 long double format on
> powerpc64le targets.
> * testsuite/27_numerics/complex/abi_tag.cc: Add u9___ieee128 to
> regex matching expected
Jonathan, could you send a fresh set of patches (or at least replacements)? I
tried installing the patches on a master branch I checked out this morning, and
I got two rejects:
--- libstdc++-v3/testsuite/util/testsuite_abi.cc
+++ libstdc++-v3/testsuite/util/testsuite_abi.cc
@@ -207,6 +207,7 @@
This adds support for the new __ieee128 long double format on
powerpc64le targets.
Most of the complexity comes from wanting a single libstdc++.so library
that contains the symbols needed by code compiled with both
-mabi=ibmlongdouble and -mabi=ieeelongdouble (and not forgetting
-mlong-double-64
19 matches
Mail list logo
