> Fixed the testcase.
It passes now, thanks!
--
Eric Botcazou
On Thu, Oct 20, 2016 at 6:50 AM, Eric Botcazou wrote:
>> Similarly on arm*/aarch64*:
>> /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/testsuite/g++.dg/cpp1z/aligned-new7.
>> C:13:41: warning: requested alignment 32 is larger than 16 [-Wattributes]
>
> Likewise on SPARC/Solaris:
>
> aligned-new7.C: In fu
> Similarly on arm*/aarch64*:
> /aci-gcc-fsf/sources/gcc-fsf/gccsrc/gcc/testsuite/g++.dg/cpp1z/aligned-new7.
> C:13:41: warning: requested alignment 32 is larger than 16 [-Wattributes]
Likewise on SPARC/Solaris:
aligned-new7.C: In function 'int main()':
aligned-new7.C:13:41: warning: requested al
Hi Jason,
On 13 October 2016 at 10:54, Andreas Schwab wrote:
> FAIL: g++.dg/cpp1z/aligned-new7.C (test for excess errors)
> Excess errors:
> /daten/aranym/gcc/gcc-20161013/gcc/testsuite/g++.dg/cpp1z/aligned-new7.C:13:41:
> warning: requested alignment 8 is larger than 2 [-Wattributes]
>
Simi
FAIL: g++.dg/cpp1z/aligned-new7.C (test for excess errors)
Excess errors:
/daten/aranym/gcc/gcc-20161013/gcc/testsuite/g++.dg/cpp1z/aligned-new7.C:13:41:
warning: requested alignment 8 is larger than 2 [-Wattributes]
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint =
It doesn't make sense to warn about placement new of over-aligned
types; most occurrences are likely to be doing this in order to
provide properly aligned memory by allocating it first and then using
the standard non-allocating placement new.
Also, the discussion of -Waligned-new on HPPA led me to
