| sourcebuild.texi (96263) | sourcebuild.texi (107590) |
|---|---|
| 1@c Copyright (C) 2002 Free Software Foundation, Inc. 2@c This is part of the GCC manual. 3@c For copying conditions, see the file gcc.texi. 4 5@node Source Tree 6@chapter Source Tree Structure and Build System 7 8This chapter describes the structure of the GCC source tree, and how --- 724 unchanged lines hidden (view full) --- 733GCC contains several test suites to help maintain compiler quality. 734Most of the runtime libraries and language front ends in GCC have test 735suites. Currently only the C language test suites are documented 736here; FIXME: document the others. 737 738@menu 739* Test Idioms:: Idioms used in test suite code. 740* C Tests:: The C language test suites. | 1@c Copyright (C) 2002 Free Software Foundation, Inc. 2@c This is part of the GCC manual. 3@c For copying conditions, see the file gcc.texi. 4 5@node Source Tree 6@chapter Source Tree Structure and Build System 7 8This chapter describes the structure of the GCC source tree, and how --- 724 unchanged lines hidden (view full) --- 733GCC contains several test suites to help maintain compiler quality. 734Most of the runtime libraries and language front ends in GCC have test 735suites. Currently only the C language test suites are documented 736here; FIXME: document the others. 737 738@menu 739* Test Idioms:: Idioms used in test suite code. 740* C Tests:: The C language test suites. |
| 741* libgcj Tests:: The Java library test suites. |
|
| 741@end menu 742 743@node Test Idioms 744@subsection Idioms Used in Test Suite Code 745 746In the @file{gcc.c-torture} test suites, test cases are commonly named 747after the date on which they were added. This allows people to tell 748at a glance whether a test failure is because of a recently found bug --- 116 unchanged lines hidden (view full) --- 865FIXME: describe this. 866@item gcc.c-torture/misc-tests 867FIXME: describe this, when it should be used for new tests and when it 868shouldn't. 869@end table 870 871FIXME: merge in @file{testsuite/README.gcc} and discuss the format of 872test cases and magic comments more. | 742@end menu 743 744@node Test Idioms 745@subsection Idioms Used in Test Suite Code 746 747In the @file{gcc.c-torture} test suites, test cases are commonly named 748after the date on which they were added. This allows people to tell 749at a glance whether a test failure is because of a recently found bug --- 116 unchanged lines hidden (view full) --- 866FIXME: describe this. 867@item gcc.c-torture/misc-tests 868FIXME: describe this, when it should be used for new tests and when it 869shouldn't. 870@end table 871 872FIXME: merge in @file{testsuite/README.gcc} and discuss the format of 873test cases and magic comments more. |
| 874 875@node libgcj Tests 876@subsection The Java library test suites. 877 878Runtime tests are executed via @samp{make check} from the @samp{testsuite} 879directory of the libjava hierarchy in the build tree. Additional runtime 880tests can be checked into this testsuite. 881 882Regression testing of the core packages in libgcj is also covered by the 883Mauve test suite. The @uref{http://sources.redhat.com/mauve/,,Mauve Project} 884develops tests for the Java Class Libraries. These tests are run as part 885of libgcj testing by specifying the location of the Mauve tree when invoking 886@samp{make}, as in @samp{make MAUVEDIR=~/mauve check}. 887 888The @uref{http://oss.software.ibm.com/developerworks/opensource/jacks/,, 889Jacks} project provides a test suite for Java compilers that can be used 890to test changes that affect the GCJ front end. There is no automated 891mechanism to run the Jacks suite as part of GCJ testing. 892 893We encourage developers to contribute test cases to Mauve and Jacks. |
|