An abstract interpretation-based timing validation of hard real-time avionics software

Thesing, Stephan; Souyris, Jean; Heckmann, Reinhold; Randimbivololona, Famantanantsoa; Langenbach, Marc; Wilhelm, Reinhard; Ferdinand, Christian

doi:10.1109/dsn.2003.1209972

Cited by 60 publications

(40 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…So far, the most successful technique has been abstract interpretation based static analysis [5,6]. It is currently used industrially on several avionics software products developed at Airbus to compute safe upper-bounds of stack consumption with AbsInt StackAnalyzer, and worst-case execution time with AbsInt aiT WCET [24,23].…”

Section: Introductionmentioning

confidence: 99%

Towards an Industrial Use of FLUCTUAT on Safety-Critical Avionics Software

Delmas

Goubault

Putot

et al. 2009

Lecture Notes in Computer Science

106

109

View full text Add to dashboard Cite

Abstract. Most modern safety-critical control programs, such as those embedded in fly-by-wire control systems, perform a lot of floating-point computations. The well-known pitfalls of IEEE 754 arithmetic make stability and accuracy analyses a requirement for this type of software. This need is traditionally addressed through a combination of testing and sophisticated intellectual analyses, but such a process is both costly and error-prone. FLUCTUAT is a static analyzer developed by CEA-LIST for studying the propagation of rounding errors in C programs. After a long time research collaboration with CEA-LIST on this tool, Airbus is now willing to use FLUCTUAT industrially, in order to automate part of the accuracy analyses of some control programs. In this paper, we present the IEEE 754 standard, the FLUCTUAT tool, the types of codes to be analyzed and the analysis methodology, together with code examples and analysis results.

show abstract

Section: Introductionmentioning

confidence: 99%

Towards an Industrial Use of FLUCTUAT on Safety-Critical Avionics Software

Delmas

Goubault

Putot

et al. 2009

Lecture Notes in Computer Science

106

109

View full text Add to dashboard Cite

show abstract

“…There are some reports on application of commercial WCET tools to analyze code for space applications [12,18,19], and in aerospace industry [20,21]. A recent case study describes experiences from applying WCET analysis to LIN and CAN communication software in cars [22].…”

Section: Wcet Analysis Overview and Related Workmentioning

confidence: 99%

Static Timing Analysis of Real-Time Operating System Code

Sandell

Ermedahl

Gustafsson

et al. 2006

Leveraging Applications of Formal Methods

View full text Add to dashboard Cite

Abstract. Methods for Worst-Case Execution Time (WCET) analysis have been known for some time, and recently commercial tools have emerged. However, the technique has so far not been much used to analyse real production codes. Here, we present a case study where static WCET analysis was used to find upper time bounds for time-critical regions in a commercial real-time operating system. The purpose was not primarily to test the accuracy of the estimates, but rather to investigate the practical difficulties that arise when applying the current WCET analysis methods to this particular kind of code. In particular, we were interested in how labor-intense the analysis becomes, measured by the number of annotations to explicitly constrain the program flow which is necessary to perform the analysis. We also make some qualitative observations regarding what a WCET analysis method would need in order to perform a both convenient and tight analysis of typical operating systems code. In a second set of experiments, we analyzed some standard WCET benchmark codes compiled with different levels of optimization. The purpose of this study was to see how the different compiler optimizations affected the precision of the analysis, and again whether it affected the level of user intervention necessary to obtain an accurate WCET estimate.

show abstract

“…These developments are reflected in the research community where numerous methods for static timing analysis have been devised, ranging from unoptimized programs executing on simple CISC processors to optimized programs on pipelined RISC processors and even uncached architectures to instruction and data caches as well as branch prediction and locking caches [33,36,19,25,21,32,45,15,28,24,13,29,41,40].…”

Section: Related Workmentioning

confidence: 99%