Re: [_Complex test 2/4] _Complex type in varargs.exp

Yao Qi
2011-05-19T13:42:54Z

On 05/19/2011 06:13 PM, Joseph S. Myers wrote:
> On Thu, 19 May 2011, Yao Qi wrote:
>
>> This patch is to add _Complex type in vararg testing.
>>
>> Run varargs.exp on i686-pc-linux-gnu, get new two KFAIL. Note that PR
>> 12776 is opened to track this problem.
>
> I think such KFAILs need to be target specific, so only for 32-bit x86 in
> this case, since for each target architecture where such a test fails it's
> going to be a separate bug in that target's ABI implementation in GDB and
> should have a separate PR.

Tests in this case also fail on armv7l-unknown-linux-gnueabi and
x86_64-unknown-linux-gnu. Shall I have to file yet another two PRs for
armv7l-unknown-linux-gnueabi and x86_64-unknown-linux-gnu respectively,
and KFAIL them to different PR separately? At least, I didn't see such
usage elsewhere in gdb testsuite.

IMO, KFAIL with target triplet works for the situation that one test
passes on all ports except one or two. However, our test fails on most
ports, different from KFAIL's typical usage.

--
Yao (é½å°§)