Faster WCET flow analysis by program slicing

Sandberg, Christer; Ermedahl, Andreas; Gustafsson, Jan; Lisper, Björn

doi:10.1145/1134650.1134666

Cited by 16 publications

(13 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…SWEET's flow analysis is based on a multi-phase approach. A program slicing is used to restrict the flow analysis to only those parts of the program that may affect the program flow [SEGL06]. A value analysis, see Subsection 3.1, combined with pattern-matching catches "easy cases" such as simple loops.…”

Section: Sweet (Swedish Execution Time Tool)mentioning

confidence: 99%

The worst-case execution-time problem—overview of methods and survey of tools

Wilhelm

Engblom²,

Ermedahl

et al. 2008

ACM Trans. Embed. Comput. Syst.

Self Cite

1,470

1,029

View full text Add to dashboard Cite

Abstract. The determination of upper bounds on execution times, commonly called WorstCase Execution Times (WCETs), is a necessary step in the development and validation process for hard real-time systems. This problem is hard if the underlying processor architecture has components such as caches, pipelines, branch prediction, and other speculative components. This article describes different approaches to this problem and surveys several commercially available tools and research prototypes.

show abstract

Section: Sweet (Swedish Execution Time Tool)mentioning

confidence: 99%

The worst-case execution-time problem—overview of methods and survey of tools

Wilhelm

Engblom²,

Ermedahl

et al. 2008

ACM Trans. Embed. Comput. Syst.

Self Cite

1,470

1,029

View full text Add to dashboard Cite

show abstract

“…Many approaches and tools of WCET analysis use graphs [21] that can be converted to XML. GLX prepares the XML-based representation for description of graphs [22].…”

Section: Discussionmentioning

confidence: 99%

A Xml-based Representation Of Timing Information For Wcet Analysis

Parsa

Sakhaei-nia

2014

J. Math. Computer Sci.

View full text Add to dashboard Cite

The Worst-Case Execution Time (WCET) analysis is an important stage in development process and verification of hard real-time systems. In this article the use of XML as a standard for exchanging timing information amongst timing analysis tools is proposed. Timing information resulted from automatic analysis of programs can be represented in XML format. Considering the type of information required for estimating the worst case execution time of programs, a set of XML tags is offered in this paper. Timing information resulted from analyzing a program by a timing analysis tool could be annotated within the program. The annotated code could be simply applied by other tools for relatively more accurate estimation of the worst case execution times. The paper also clears the way for future studies on using XML-based representation for extraction of information.

show abstract

“…We will also do the flow analysis on ALF, using SWEET's powerful flow analysis methods [23,24,25]. The result will be given as constraints on the number of times different basic blocks of the ALF code can be executed and edges of the control flow graph can be followed.…”

Section: Methodsmentioning

confidence: 99%

Approximate Worst-Case Execution Time Analysis for Early Stage Embedded Systems Development

Gustafsson

Altenbernd²,

Ermedahl

et al. 2009

Software Technologies for Embedded and Ubiquitous Systems

Self Cite

View full text Add to dashboard Cite

Abstract.A Worst-Case Execution Time (WCET) analysis finds upper bounds for the execution time of programs. Reliable WCET estimates are essential in the development of safety-critical embedded systems, where failures to meet timing deadlines can have catastrophic consequences.Traditionally, WCET analysis is applied only in the late stages of embedded system software development. This is problematic, since WCET estimates are often needed already in early stages of system development, for example as inputs to various kinds of high-level embedded system engineering tools such as modelling and component frameworks, scheduling analyses, timed automata, etc. Early WCET estimates are also useful for selecting a suitable processor configuration (CPU, memory, peripherals, etc.) for the embedded system.If early WCET estimates are missing, many of these early design decisions have to be made using experience and "gut feeling". If the final executable violates the timing bounds assumed in earlier system development stages, it may result in costly system re-design. This paper presents a novel method to derive approximate WCET estimates at early stages of the software development process. The method is currently being implemented and evaluated. The method should be applicable to a large variety of software engineering tools and hardware platforms used in embedded system development, leading to shorter development times and more reliable embedded software.

show abstract

Faster WCET flow analysis by program slicing

Cited by 16 publications

References 23 publications

The worst-case execution-time problem—overview of methods and survey of tools

The worst-case execution-time problem—overview of methods and survey of tools

A Xml-based Representation Of Timing Information For Wcet Analysis

Approximate Worst-Case Execution Time Analysis for Early Stage Embedded Systems Development

Contact Info

Product

Resources

About