Re: [arm-gnu] Compiling Safety Related Systems?

[Mark Mitchell <mark@xxxxxxxxxxxxxxxx>]

Charles Manning wrote:

>> - error/defect information (for a certain build)
> 
> Perhaps the only real concern.

Every CodeSourcery build (Lite Edition and our commercial products) goes
through a test process that involves hundreds of thousands, or,
depending on the configuration, millions of tests.  Our engineers
examine these results, and investigate causes of failure (which are
often things like insufficient memory on a target system, or a Linux
kernel with a defect).  The results are logged with each build that we
ship so that we can later reexamine test results from a previous build.

Interpreting the test results is not easy, and some of the tests are
proprietary (to us and/or to third parties), so we do not post this
information.  But, we do have it and can provide customers with
information about our processes.

Our compilers certainly do have bugs (as do all versions of GCC, and, I
expect, all versions of all C/C++ compilers).  However, we work with our
customers to resolve critical defects as quickly as possible.

As one reference point, I'll mention that Wind River's VxWorks operating
system, which is routinely used in safety-critical applications, ships
with versions of GCC built and supported by CodeSourcery.  (These are
not the same binaries that we provide as commercial products, but they
are built using substantially similar processes.)

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@xxxxxxxxxxxxxxxx
(650) 331-3385 x713