GCC Testing

This page is a test plan for Linaro GCC, and includes such things as the environment tested under, systems tested, and test steps

Environment

GCC uses the default environment.

Configurations

The following configurations are built:

  • i686 using --with-cpu=i686

  • x86_64 using default options
  • ARM variants
    • Cortex-A9 with NEON using --with-mode=thumb --with-arch=armv7-a --with-tune=cortex-a9 --with-float=softfp --with-fpu=neon

    • Cortex-A8 with VFP using --with-mode=thumb --with-arch=armv7-a --with-float=softfp --with-fpu=vpfv3-d16

The Cortex-A9 configuration is optimised for the A9 but will still run, including errata fixes, on the A8. The Cortex-A8 configuration is the same as the Ubuntu Maverick default.

These configurations are stored at:

The 'rn' suffix gives the configuration revision which is also appended to every build output.

All hosts enable C, C++, Obj-C, and Obj-C++. i686 and x86_64 hosts enable Fortran and Java. GCC 4.5 targets enable LTO.

All builds are bootstrap builds. Future builds should be PGO bootstrap builds.

The particular configuration used is recorded at the top of each configure run file such as:

Testing

GCC is tested at each release using:

  • The GCC testsuite, as run by make check

  • The libstdc++ testsuite, as run by make check-target-libstdc++-v3

Future tests may include:

  • Building Python
  • Building EGLIBC

Results are saved such as

The detailed logs gcc.log and gcc.sum are also saved.

Test results are compared for regressions against the last release using the 'testcompare' tool such as

The regressions are categorised as:

  • Correctness regressions, especially
    • Limits failures
  • Performance regressions, especially
    • Vectoriser regressions

WorkingGroups/ToolChain/GCC/Testing (last modified 2012-12-04 23:15:43)