We frequently discuss compiler qualification and its importance in making sure that your safety-critical components work properly and adhere to safety standards. But what actually is compiler qualification? How does it work?
It’s the end of another decade. One that saw supercomputer performance grow by a factor of 100, so Moore’s law is still going strong. Almost as old as Moore’s law, the C language and SuperTest are also alive and kicking. With the recent C18 and SuperTest Vermeer release, both are fit and ready for the 2020s, during which we confidently expect them to continue dominating the system software market.
Open-source software is everywhere – in the global IT infrastructure, in our PCs and in our cars. Open-source hardware, on the other hand, is far less visible. With the emergence of RISC-V that may be about to change. While we see great potential for open-source architectures, it does mean that compiler qualification and validation will become even more critical.
The realisation that qualified compilers are a necessity in the development of safety-critical applications is finally hitting home in the automotive industry. Yet not every company has the capacity to qualify a compiler themselves for their specific configuration and compiler options – their use case. You may be using a pre-qualified compiler, but are you sure that matches the use case that your application is built with? This is why we introduce our Tailor-Made Compiler Qualification Service – for your configuration, your options and your environment.
As programmers, we all make mistakes. Writing first-time-right C or C++ code is very unusual. One important function of a compiler is to spot these errors, issue diagnostics and prevent object code generation. If a compiler fails to detect source code errors they will propagate to the application, where your test department or worse still your customer will eventually find them. In safety-critical applications it could have serious consequences.
It may sound as too obvious, but there is a big difference between the source code and the compiler generated code for an application. For one, compiler generated code is more complicated, because it often includes duplicated, and specialized, source code. So, why is it that when it comes to safety testing code according to the ISO 26262 standard, they are often treated as the same?
The Renault Co-Innovation Days are organized by AutomotiveNL, Renault and the Dutch Embassy at the Renault Technocentre and the Dutch Residency in Paris. Solid Sands will exhibit here on the 25th and 26th of June 2019.
As you may have seen on social media last week, the latest SuperTest release is here. It’s called SuperTest Vermeer Release and we’re very proud of it. Why? Because it reflects one of the things that the Dutch painter Johannes Vermeer was most famous for – an...
In all our years of compiler testing, there’s one thing we can say for certain – no compiler is perfect. It’s inevitable that whenever you really put a new or old compiler through its paces you’ll find an error. That’s why compiler qualification for safety-critical...
We were recently asked if SuperTest is suitable for ‘white-box’ testing, in addition to its normal role as a ‘black-box’ testing platform. As legitimate as this question is, it reminded us that there might be some confusion surrounding black-box and white-box testing...