On Tue, 2 Jun 2015, Michael Meissner wrote:
> 4) Add float128 versions of the basic math libraries. For this it will
>probably be simpler if we can force long double to be IEEE 128-bit so you
>don't have to change as much code, but you want to suppress whatever check
>there will be to
On Tue, Jun 02, 2015 at 08:14:12PM +, Joseph Myers wrote:
> On Tue, 2 Jun 2015, Michael Meissner wrote:
>
> > On Tue, Jun 02, 2015 at 05:55:10PM +, Joseph Myers wrote:
> > > Is the use of FRACTIONAL_FLOAT_MODE to avoid iterations over
> > > floating-point modes including these modes when
On Tue, Jun 2, 2015 at 4:14 PM, Joseph Myers wrote:
> On Tue, 2 Jun 2015, Michael Meissner wrote:
>
>> On Tue, Jun 02, 2015 at 05:55:10PM +, Joseph Myers wrote:
>> > Is the use of FRACTIONAL_FLOAT_MODE to avoid iterations over
>> > floating-point modes including these modes when they shouldn't
On Tue, 2 Jun 2015, Michael Meissner wrote:
> On Tue, Jun 02, 2015 at 05:55:10PM +, Joseph Myers wrote:
> > Is the use of FRACTIONAL_FLOAT_MODE to avoid iterations over
> > floating-point modes including these modes when they shouldn't, as
> > discussed previously?
> >
> > If so, how do you
On Tue, Jun 2, 2015 at 2:27 PM, Michael Meissner
wrote:
> On Tue, Jun 02, 2015 at 01:43:08PM -0400, David Edelsohn wrote:
>> Mike,
>>
>> What is the purpose of the TARGET_LONG_DOUBLE_128 change in
>> rs6000_hard_regno_mode_ok()?
>>
>> + /* If we don't allow 128-bit binary floating point, disallow
On Tue, Jun 02, 2015 at 05:55:10PM +, Joseph Myers wrote:
> Is the use of FRACTIONAL_FLOAT_MODE to avoid iterations over
> floating-point modes including these modes when they shouldn't, as
> discussed previously?
>
> If so, how do you deal (in subsequent patches?) with iterations that
> *s
On Tue, Jun 02, 2015 at 01:43:08PM -0400, David Edelsohn wrote:
> Mike,
>
> What is the purpose of the TARGET_LONG_DOUBLE_128 change in
> rs6000_hard_regno_mode_ok()?
>
> + /* If we don't allow 128-bit binary floating point, disallow the 128-bit
> + types from going in any registers. Simila
Is the use of FRACTIONAL_FLOAT_MODE to avoid iterations over
floating-point modes including these modes when they shouldn't, as
discussed previously?
If so, how do you deal (in subsequent patches?) with iterations that
*should* include these modes? In particular, where libgcc uses
__LIBGCC__*
On Fri, May 22, 2015 at 5:24 PM, Michael Meissner
wrote:
> This patch is the first in a series of patches that will eventually add
> support
> for IEEE 128-bit floating point support to the PowerPC GCC compiler. At the
> current time, we do not plan to change the default for long double. I adde
This patch is the first in a series of patches that will eventually add support
for IEEE 128-bit floating point support to the PowerPC GCC compiler. At the
current time, we do not plan to change the default for long double. I added a
new type keyword (__float128) to get access to IEEE 128-bit flo
10 matches
Mail list logo
