You are here: Home / RTLWS 1999-2017 / RTLWS Submitted Papers / 
2024-11-23 - 21:14

Dates and Events:

OSADL Articles:

2024-10-02 12:00

Linux is now an RTOS!

PREEMPT_RT is mainline - What's next?


2023-11-12 12:00

Open Source License Obligations Checklists even better now

Import the checklists to other tools, create context diffs and merged lists


2023-03-01 12:00

Embedded Linux distributions

Results of the online "wish list"


2022-01-13 12:00

Phase #3 of OSADL project on OPC UA PubSub over TSN successfully completed

Another important milestone on the way to interoperable Open Source real-time Ethernet has been reached


2021-02-09 12:00

Open Source OPC UA PubSub over TSN project phase #3 launched

Letter of Intent with call for participation is now available



Real Time Linux Workshops

1999 - 2000 - 2001 - 2002 - 2003 - 2004 - 2005 - 2006 - 2007 - 2008 - 2009 - 2010 - 2011 - 2012 - 2013 - 2014 - 2015

15th Real Time Linux Workshop, October 28 to 31, 2013 at the Dipartimento Tecnologie Innovative, Scuola Universitaria Professionale della Svizzera Italiana in Lugano-Manno, Switzerland

Announcement - Call for participation (ASCII)Hotels - Directions - AgendaPaper Abstracts - Presentations - Registration - Abstract Submission - Sponsors - Gallery

Qualifying a closed-source COTS compiler

Wei Ming, Beijing Shenzhou Aerospace Software Technology Co., Ltd., China

There are many critical systems containing complex software for which the implementation language of choice is C in many cases (DO 178 actually suggest Ada or C). Some current software-controlled embedded aerospace systems need to be qualified to DO 178C Level A or Level B.

At this level it is recommended that developer use certificated compilers. But due to business considerations, cost, and other factors, aerospace software development in China currently only use closed source/proprietary compilers, which are no longer being maintained.

We do not have access to the tools development process specification respectively the developer TOR, but we can do extensive tools testing according to DO330 section 6.14: "The objectives of tool testing are to execute the Tool Executable Object Code". While testing generally can not proof freedom from faults it is acknowledged that compilers can not be proven correct (IEC 61508-7 Ed2 C 4.4) states: "It is also known, presently, that no method exists to prove the correctness for all tool or translator parts." Thus systematic testing as well as "field-data" is an essential part of translator tools qualification.

This paper description different testing methods applicable to closed source COTS tool to provide acceptable assurance of compiler correctness for a well-defined and limited language/feature subset allowing to mitigate the risks posed by the use of a legacy compiler.