Re: [commit] testsuite: KFAIL gdb.cp/static-method.exp [Re: Regression for gdb.base/sigstep.exp with .debug_types]

[Jan Kratochvil <jan.kratochvil@redhat.com>]

On Sun, 11 Dec 2011 03:47:42 +0100, Joel Brobecker wrote:
> > Therefore KFAILed it.  (Not sure if it should be XFAIL or KFAIl but it does
> > not matter much.)
> 
> If it's not a bug in GDB, then I think it should be an XFAIL...

IMO it depends on whether one considers "our" to be just GDB or whether "our"
is the whole GNU Toolchain.

Therefore if "our" is just GDB I can change all the already existing KFAILs
with gcc/
gdb.cp/ptype-cv-cp.exp:setup_kfail "gcc/45997" *-*-*
gdb.cp/temargs.exp:setup_kfail gcc/49366 "*-*-*"
gdb.cp/temargs.exp:} else { setup_kfail gcc/49546 "*-*-*" }
gdb.cp/temargs.exp:} else { setup_kfail gcc/49546 "*-*-*" }
gdb.python/py-type.exp:    setup_kfail "gcc/41736" *-*-*

into XFAILs.  So far both ways were in use:
gdb.gdb/selftest.exp:		    setup_xfail "*-*-*" gcc/26475
gdb.java/jmain.exp:	setup_xfail *-*-* gcc/16439
gdb.java/jmain.exp:		setup_xfail *-*-* gcc/16439
gdb.java/jprint.exp:    setup_xfail *-*-* gcc/43260


Thanks,
Jan