Re: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-16 Thread Segher Boessenkool
Hi! On Tue, Aug 16, 2022 at 08:07:48PM +0200, Jakub Jelinek wrote: > On Thu, Aug 11, 2022 at 08:44:17PM +, Joseph Myers wrote: > > On Thu, 11 Aug 2022, Michael Meissner via Gcc-patches wrote: > > > In looking at it, I now believe that the type for _Float128 and __float128 > > > should always b

Re: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-16 Thread Jakub Jelinek via Gcc-patches
On Thu, Aug 11, 2022 at 08:44:17PM +, Joseph Myers wrote: > On Thu, 11 Aug 2022, Michael Meissner via Gcc-patches wrote: > > > In looking at it, I now believe that the type for _Float128 and __float128 > > should always be the same within the compiler. Whether we would continue to > > use the

Re: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-11 Thread Joseph Myers
On Thu, 11 Aug 2022, Michael Meissner via Gcc-patches wrote: > In looking at it, I now believe that the type for _Float128 and __float128 > should always be the same within the compiler. Whether we would continue to > use the same type for long double and _Float128/__float128 remains to be seen.

Re: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-11 Thread Michael Meissner via Gcc-patches
On Wed, Aug 10, 2022 at 12:03:16PM -0500, Segher Boessenkool wrote: > On Wed, Aug 10, 2022 at 02:23:27AM -0400, Michael Meissner wrote: > > On Fri, Aug 05, 2022 at 01:19:05PM -0500, Segher Boessenkool wrote: > > > On Thu, Jul 28, 2022 at 12:43:49AM -0400, Michael Meissner wrote: > > > > These patch

Re: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-10 Thread Segher Boessenkool
On Wed, Aug 10, 2022 at 02:23:27AM -0400, Michael Meissner wrote: > On Fri, Aug 05, 2022 at 01:19:05PM -0500, Segher Boessenkool wrote: > > On Thu, Jul 28, 2022 at 12:43:49AM -0400, Michael Meissner wrote: > > > These patches lay the foundation for a set of follow-on patches that will > > > change

Re: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-09 Thread Michael Meissner via Gcc-patches
On Fri, Aug 05, 2022 at 01:19:05PM -0500, Segher Boessenkool wrote: > On Thu, Jul 28, 2022 at 12:43:49AM -0400, Michael Meissner wrote: > > These patches lay the foundation for a set of follow-on patches that will > > change the internal handling of 128-bit floating point types in GCC. In the > >

Re: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-05 Thread Segher Boessenkool
On Thu, Jul 28, 2022 at 12:43:49AM -0400, Michael Meissner wrote: > These patches lay the foundation for a set of follow-on patches that will > change the internal handling of 128-bit floating point types in GCC. In the > future patches, I hope to change the compiler to always use KFmode for the >

Ping: [PATCH 0/5] IEEE 128-bit built-in overload support.

2022-08-03 Thread Michael Meissner via Gcc-patches
Ping patches. Patch #1 of 5. | Date: Thu, 28 Jul 2022 00:47:13 -0400 | Subject: [PATCH 1/5] IEEE 128-bit built-in overload support. | Message-ID: Patch #2 of 5. | Date: Thu, 28 Jul 2022 00:48:51 -0400 | Subject: [PATCH 2/5] Support IEEE 128-bit overload round_to_odd built-in functions. | Messag

[PATCH 0/5] IEEE 128-bit built-in overload support.

2022-07-27 Thread Michael Meissner via Gcc-patches
The following patches add support for doing built-in function overloading between the two 128-bit IEEE types (i.e. _Float182/__float128 using KFmode and when long double uses the IEEE 128-bit encoding with TFmode). These patches lay the foundation for a set of follow-on patches that will change th