On Mon, Jan 20, 2020 at 9:53 AM Ian Lance Taylor wrote:
>
> kamlesh kumar writes:
>
> > yes, current expected entry is wrong and
> > Nick's patch corrects that.
>
> Thanks. Nick, the patch is OK.
>
> Ian
> >> > libiberty/ChangeLog
> >> > 2020-01-20 Nick Clifton
> >> >
> >> > * testsuit
kamlesh kumar writes:
> yes, current expected entry is wrong and
> Nick's patch corrects that.
Thanks. Nick, the patch is OK.
Ian
> On Mon, Jan 20, 2020 at 9:29 PM Ian Lance Taylor wrote:
>
>> Nick Clifton writes:
>>
>> > Hi Ian,
>> >
>> > The libiberty testsuite in the gcc mainline is cu
yes, current expected entry is wrong and
Nick's patch corrects that.
./kamlesh
On Mon, Jan 20, 2020 at 9:29 PM Ian Lance Taylor wrote:
> Nick Clifton writes:
>
> > Hi Ian,
> >
> > The libiberty testsuite in the gcc mainline is currently failing on
> > the last test:
> >
> > FAIL at li
Nick Clifton writes:
> Hi Ian,
>
> The libiberty testsuite in the gcc mainline is currently failing on
> the last test:
>
> FAIL at line 1452, options :
> in: _Z3fooILPv0EEvPN9enable_ifIXeqT_LDnEEvE4typeE
> out: void foo<(void*)0>(enable_if<((void*)0)==(decltype(nullptr)),
> voi
Hi Ian,
The libiberty testsuite in the gcc mainline is currently failing on
the last test:
FAIL at line 1452, options :
in: _Z3fooILPv0EEvPN9enable_ifIXeqT_LDnEEvE4typeE
out: void foo<(void*)0>(enable_if<((void*)0)==(decltype(nullptr)),
void>::type*)
exp: void foo<(void*)0>(
