8sa1-gcc

History

Zack Weinberg 47035bb8d2 More tests for uninitialized variable warnings From-SVN: r25770		1999-03-14 20:19:03 +00:00
..
special
980211-1.c
980217-1.c
980226-1.c
980312-1.c
980313-1.c
980414-1.c
980502-1.c
980520-1.c
980523-1.c
980526-1.c
980709-1.c
980816-1.c
980827-1.c
990117-1.c
990119-1.c
990130-1.c
990213-1.c
990213-2.c
990214-1.c
990228-1.c	New test; derived from glibc regression	1999-02-28 15:05:16 +00:00
bf-spl1.c
clobbers.c
cpp-if1.c	Minor tweaks to testing harness	1999-02-28 15:05:41 +00:00
cpp-if2.c	Minor tweaks to testing harness	1999-02-28 15:05:41 +00:00
cpp-if3.c
cpp-mi.c
cpp-mic.h
cpp-micc.h
dg.exp
dll-1.c
dll-2.c
dll-3.c
dll-4.c
ifelse-1.c
README
setjmp-1.c	New test, for spurious "variable may be clobbered by `longjmp' or` vfork'"	1999-03-14 09:18:03 +00:00
splet-1.c
struct-ret-1.c
switch-1.c
ultrasp1.c
uninit-1.c	* empty log message *	1999-03-11 16:00:03 +00:00
uninit-2.c	Tests for various kinds of spurious uninit variable warning.	1999-03-11 16:00:04 +00:00
uninit-3.c	Tests for various kinds of spurious uninit variable warning.	1999-03-11 16:00:04 +00:00
uninit-4.c	Tests for various kinds of spurious uninit variable warning.	1999-03-11 16:00:04 +00:00
uninit-5.c	More tests for uninitialized variable warnings	1999-03-14 20:19:03 +00:00
uninit-6.c	More tests for uninitialized variable warnings	1999-03-14 20:19:03 +00:00
uninit-8.c	More tests for uninitialized variable warnings	1999-03-14 20:19:03 +00:00
uninit-9.c	More tests for uninitialized variable warnings	1999-03-14 20:19:03 +00:00

README

Notes for testsuite/gcc.dg.

1) There should be only one driver, dg.exp.

2) Try to organize the tests by topic using file name prefixes.

   Eg: All bitfield tests are named "bf-*.c".

   This lets the person running the tests choose particular sets of tests to
   run easily (using wildcards).

   Eg: make check RUNTESTFLAGS='dg.exp=bf-*.c'

3) Remember DOS file name restrictions (8.3).  Sigh.

4) Send bugs, comments, etc. to dje@cygnus.com.