• Under Construction - March 25,, 2002
• Daily Build Results
• Daily Build Stats

AutoBuild System Information

"Application" Field Information

This field in the autobuild system, which specifies that name of a specific application that was built from a CVS repository. Usually this field is blank, as all the applications within a CVS repository are built by default.

Baseline Information

A "baseline" is toolchain, that is used to build other toolchain(s). A baseline is usually only built with components which are from major stable releases. Any deficiencies in the "baseline" will usually show up in the created toolchain. In order to isolate these problems, a toolchain is usually built with more than one "baseline". For example, on Nov 19, 2001, gdb was built from a clean cvs snapshot on an alphaev56-unknown-linux-gnu and i686-pc-linux-gnu systems, using six "baselines". The same six "baselines" where used on both architectures makes certian that we are doing a like comparison, when looking at the testsuite results. As you can see from the results file, that same source gdb built with different "baseline"s produced different testsuite results. On the i686-pc-linux-gnu system, it appears that the "basic baseline" has the best testsuite results, which uses the egcs 1.1.2 compiler. On the alphaev56-unknown-linux-gnu system, it appears that the "bootstrap-gcc_3.0.2 baseline" has the best testsuite results, which uses the gcc 3.0.2 compiler.

Build Machine System Type

The canonical "system type(s)" used to identify the type of system that was used to build the ToolChain.

CVSRepository Information

• gcc-2_95-branch

• gcc-3_0-branch

• gcc-head-branch

• glibc

• src

• toolchain (a.k.a uberbaum)

CVS Snapshot Information

All CVS-Snapshots are taken at 00:05 a.m EST (GMT-5) on the date of the snapshot.

Logs

Number of Job Slots

GNU `make' knows how to execute several commands at once. The number of commands to execute at once is called the "number of job slots". For more information, please see, the info page from make.info.gz, in the GNU "make" package, that is titled "Parallel Execution".

System Type Information

The "system type" is in the form of CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM or in some cases, the newer four-part form of CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM. The fields of the "system type" are as follows:

• CPU is the type of processor. This is typically something like "i386" or "arm". More specific variants are used as well, such as `armv4l' to indicate a little endian version 4 ARM processor.
• MANUFACTURER is a somewhat freeform field which indicates the manufacturer of the system. This is often simply "unknown". Other common strings are "pc" for an IBM PC compatible system, or the name of a workstation vendor, such as "sun".
• KERNEL is used mainly for GNU/Linux. A typical GNU/Linux configuration name is "i586-pc-linux-gnu". In this case the kernel, "linux", is separated from the operating system, `gnu'.
• OPERATING_SYSTEM is the name of the operating system which is run on the system. This will be something like "solaris2.5" or "irix6.3". There is no particular restriction on the version number, and strings like "aix4.1.4.0" are seen. For an embedded system, which has no operating system, this field normally indicates the type of object file format, such as "elf" or "coff".

When using a "system type", it is normally not necessary to specify an entire name. In particular, the manufacturer field is often omitted, leading to strings such as "i386-linux" or "sparc-sunos". There are also short aliases for many system names; for example, "decstation" can be given on the command line instead of "mips-dec-ultrix4.2" The shell script "config.sub", when it is called will translate these shortened strings into the canonical form during the "configuration" process.

It is common to see canonical "system type"(s), which identify a target architecture, that is not labeled with BUILD-TYPE (--build=), HOST-TYPE (--host=) or TARGET-TYPE (--target=), but it is possible to infer from the number and order of "system type"s the corresponding labels:

• Single canonical "system type" is a native toolchain, which the BUILD-TYPE, HOST-TYPE and TARGET-TYPE are the same.
• Two canonical "system type"s is a cross compiler. The first "system type" is the BUILD-TYPE and HOST-TYPE. The second "system-type" is the TARGET-TYPE.
• Three canonical "system type"s is sometimes called a Canadian cross compiler. The first "system type" is the BUILD-TYPE. The second "system type" is and HOST-TYPE. The third "system-type" is the TARGET-TYPE.

Testsuite Information

ToolChain System Type(s) Information

The GNU toolchains use three canonical "system type(s)" to identify the toolchain's architecture:

• BUILD-TYPE - This is the type of system that was used to configure and build the toolchain.
• HOST-TYPE - This is the type of system on which the toolchain can execute.
• TARGET-TYPE - This is the type of system on which the binaries generated by the toolchain can execute.