This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A testcase library
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: drow at mvista dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 23 Dec 02 20:45:36 EST
- Subject: Re: A testcase library
Suppose that GDB is debugging a program, and the information it needs
is simply missing from the debug info. Zilch, nada, absolutely no way
to recover it. That's an XFAIL.
Suppose that a testcase is for a new bug that no one's figured out how
to fix yet. That's a KFAIL. All KFAILs are required to have an open PR
associated with them, at least in GDB-land.
The difference, in theory, is that KFAILs represent real problems that
have not been fixed; and XFAILs represent "expected" failures, problems
in the system or tools that can not be fixed in the program-under-test.
I still don't get it. Your first example sounds like something that's not
a bug at all, in which case why would the "test case" still be in the suite?