Facilitating worst-case execution times analysis for optimized code

Engblom, Jakob; Ermedahl, Andreas; Altenbernd, P.

doi:10.1109/emwrts.1998.685079

Cited by 40 publications

(27 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Previous publications have already shown that it is relevant to combine WCET optimization with other criteria like e. g. code size. Using objectives and handlers, our -+ ------ [7] + --+ -- [12] --+ + ---+ [17,18] -+ + + ---+ [13] ----+ + [16] --+ + ± --+ …”

Section: Discussion Of the Structure Of Wccmentioning

confidence: 99%

See 1 more Smart Citation

Design of a WCET-Aware C Compiler

Falk

Lokuciejewski

Theiling

2006

2006 IEEE/ACM/IFIP Workshop on Embedded Systems for Real Time Multimedia

View full text Add to dashboard Cite

show abstract

Section: Discussion Of the Structure Of Wccmentioning

confidence: 99%

“…In order to keep track of the influence of compiler optimization on high-level flow facts, [7] proposes co-transformation of flow facts. However, the cotransformer has never reached a fully working state, and several standard compiler optimizations can not be modeled at all due to insufficient data structures.…”

Section: Related Workmentioning

confidence: 99%

Design of a WCET-Aware C Compiler

Falk

Lokuciejewski

Theiling

2006

2006 IEEE/ACM/IFIP Workshop on Embedded Systems for Real Time Multimedia

View full text Add to dashboard Cite

show abstract

“…There is already a great deal of analysis available including [4,16], and Engblom provides a useful survey of these analyses in [5]. These approaches can be tailored for our use by taking advantage of the fact that software is written in a particularly disciplined way for the safetycritical domain.…”

Section: Worst-case Execution Time Analysismentioning

confidence: 99%

“…• there are greater variations in the execution times of the software [4]; • it is harder to deduce the actual WCET of the software as the analysis would have to include a model of the cache mechanism-it could be assumed that all memory accesses result in a cache miss but this gives results much greater than the actual WCET, leading to wasted resources [4]; • the more complex the processor is, the harder it is to validate the models used and the higher the likelihood of systematic design errors (in the processor and the accompanying models) [5].…”

Section: Memory Accessmentioning

confidence: 99%

Use of Modern Processors in Safety-Critical Applications

Bate

Conmy²,

Kelly³

et al. 2001

The Computer Journal

View full text Add to dashboard Cite

This paper investigates the implications of using modern superscalar processors in the safety-critical domain. Firstly, a description of current certification practice and devices is given as background. This is followed by an exposition of the certification argument for a processor when used in a safetycritical application. Throughout the presentation of the argument two types of modern processor are considered, commercial off-the-shelf (COTS) processors and purpose-designed bespoke devices. This allows the elaboration of positive and negative features of processors that can be used as part of the selection (for COTS) or design (for bespoke) process.

show abstract

“…Annotating the machine code is not a desirable solution as it requires that the programmer studies the compiler-generated machine code and understands the code transformations done by the compiler. Therefore, if there is need for annotations, the preferred solution is to annotate the program source with flow information and to transform the flow information automatically, while optimizing the code (Kirner and Puschner 2001;Engblom et al 1998).…”

Section: Introductionmentioning

confidence: 99%

Transforming flow information during code optimization for timing analysis

2010

View full text Add to dashboard Cite

The steadily growing embedded-systems market comprises many application domains in which real-time constraints must be satisfied. To guarantee that these constraints are met, the analysis of the worst-case execution time (WCET) of software components is mandatory. In general WCET analysis needs additional control-flow information, which may be provided manually by the user or calculated automatically by program analysis. For flexibility and simplicity reasons it is desirable to specify the flow information at the same level at which the program is developed, i.e., at the source level. In contrast, to obtain precise WCET bounds the WCET analysis has to be performed at machine-code level. Mapping and transforming the flow information from the source-level down to the machine code, where flow information is used in the WCET analysis, is challenging, even more so if the compiler generates highly optimized code.In this article we present a method for transforming flow information from source code to machine code. To obtain a mapping that is safe and accurate, flow information is transformed in parallel to code transformations performed by an optimizing compiler. This mapping is not only useful for transforming manual code annotations but also if platform-independent flow information is automatically calculated at the source level. We show that our method can be applied to every type of semantics-preserving code transformation. The precision of this flow-information transformation allows its users to calculate tight WCET bounds.

show abstract

Facilitating worst-case execution times analysis for optimized code

Cited by 40 publications

References 15 publications

Design of a WCET-Aware C Compiler

Design of a WCET-Aware C Compiler

Use of Modern Processors in Safety-Critical Applications

Transforming flow information during code optimization for timing analysis

Contact Info

Product

Resources

About