GCC 2.95 other tests

Package/Feature Testing

In addition to regression testing it is important to perform tests on larger software packages. The key packages used for GCC 2.95 testing are the Linux kernel, GNU C library, Red Hat 6.0 sources and the LAPACK library.

Platform	linux-2.2.10	glibc-2.1.1	redhat-6.0	lapack
alphaev6-unknown-linux-gnu	UNTESTED	OK	UNTESTED	complex failures
hppa1.1-hp-hpux10.20	N/A	N/A	N/A	-O2 OK -O3 -funroll-loops fails
i586-unknown-linux-gnu	OK	OK	UNTESTED	UNTESTED
i686-unknown-linux-gnu	OK	OK	compat-binutils compat-egcs kdelibs korganizer python sgml-tools	OK
mips-sgi-irix6.5	N/A	N/A	N/A	complex failures
powerpc-unknown-linux-gnu	2.2.6 OK	OK	UNTESTED	OK
sparc-sun-solaris2.5	N/A	N/A	N/A	OK
sparc-unknown-linux-gnu	UNTESTED	OK	UNTESTED	UNTESTED

Package testing notes

Note the linux kernel, modules and related code must be compiled with -fno-strict-aliasing as the linux kernel violates ANSI/ISO C standards used to perform type based alias analysis.

GCC 2.95 has known bugs accessing complex values on 64bit targets. This particularly effects Fortran code (such as lapack) on Alphas, MIPS potentially other 64bit platforms.

For questions related to the use of GCC, please consult these web pages and the GCC manuals. If that fails, the gcc-help@gcc.gnu.org mailing list might help. Comments on these web pages and the development of GCC are welcome on our developer list at gcc@gcc.gnu.org. All of our lists have public archives.

Copyright (C) Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

These pages are maintained by the GCC team. Last modified 2022-10-26.