Using libraries safely is your responsibility

Functional Safety standards require that the user of the library takes responsibility for the library, even if it comes from a third party. Library code becomes part of your safety-critical target device, so it has to be verified as fit for purpose. As the application...

Not all test suites are created equal

We are often asked what differentiates SuperTest from the GCC and LLVM test suites. If you are using the LLVM or GCC test suite, why would you use SuperTest as well? Apart from the obvious answer “more testing, preferably using tests with different origins, is...

The risks of invalid error messaging

The fundamental measure of any compiler is its ability to generate high-quality, functionally correct, executable code. But equally important is its ability to generate valid, well annotated, error messages when the source code it parses is poorly constructed. Invalid...

Library code is part of your safety critical application

Writing code for your safety-critical application requires a great deal of care and attention. But above all it requires highly effective verification. That not only applies to the code you write. It also applies to any standard libraries you use, because standard...

Webinar: Language subsetting and compiler qualification

In this blog, we promote the joint webinar we are running with BUGSENG. The webinar topic is: “Language Subsetting and Compiler Qualification in the Development of Software for Safety-Critical Systems”. It will run on Thursday, 17 September at 11:00-12:00 CEST...