> On Jul 1, 2016, at 2:49 PM, Joseph Myers wrote:
>
> On Fri, 1 Jul 2016, Bill Schmidt wrote:
>
>> +/* { dg-additional-options "-mfloat128 -mvsx" { target powerpc*-*-* } } */
>
> I still think you should be using { dg-add-options float128 }, via
> defining add_options_for_float128, rather tha
On Fri, Jul 1, 2016 at 3:39 PM, Bill Schmidt
wrote:
> Hi,
>
> This changes my previous patch to use a separate base_quadfloat_support
> effective target that can be used in conjunction with either the float128
> or __float128 effective targets, and modifies the tests accordingly.
> I dropped addin
On Fri, 1 Jul 2016, Bill Schmidt wrote:
> +/* { dg-additional-options "-mfloat128 -mvsx" { target powerpc*-*-* } } */
I still think you should be using { dg-add-options float128 }, via
defining add_options_for_float128, rather than hardcoding these options
in individual tests.
--
Joseph S. My
Hi,
This changes my previous patch to use a separate base_quadfloat_support
effective target that can be used in conjunction with either the float128
or __float128 effective targets, and modifies the tests accordingly.
I dropped adding support for float128-exact-underflow.c for now; that can
be ad
