This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Test cases and expecting failures


On Thu, 26 Sep 2002, D.Venkatasubramanian, Noida wrote:
> Another observation I made was that, in gcc.c-torture directory,
> the test cases are unresolved by making a <test-case>.x file, but
>  such files weren't present in other directories. I found similar
> "Commands" formatted as comments in test cases itself in other
> directories. Any specific reason for this difference?

History, it seems; they're both different dejagnu-based
test-harnesses.  Read all of the dejagnu documentation and all
of the gcc *.exp files.

> For example in File : "gcc.dg/wint_t-1.c"
> /* { dg-excess-errors "Newlib has no wchar.h" { target mmix-knuth-mmixware
> cris-*-elf } } */
>
> I presume that to add some other target, say xxx-*-*,
> I would change this to,
>
> /* { dg-excess-errors "Newlib has no wchar.h" { target mmix-knuth-mmixware
> cris-*-elf xxx-*-* } } */
>
> Am I thinking correctly?

Well, yes, but rather than ask here, you should read the dejagnu
documentation and the documentation hidden in the comments
(gah!) in /usr/share/dejagnu/dg.exp (assuming dejagnu was built
with --prefix=/usr).

> And what if I only want this to happen if
> xxx-*-* is built with newlib.

Often the *-*-elf targets are built with newlib.  I guess it can
depend on the target.

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]