2008
DOI: 10.1145/1347375.1347389
|View full text |Cite
|
Sign up to set email alerts
|

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

Abstract: 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.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

1
1,029
0
3

Year Published

2008
2008
2017
2017

Publication Types

Select...
7
1
1

Relationship

0
9

Authors

Journals

citations
Cited by 1,460 publications
(1,115 citation statements)
references
References 80 publications
1
1,029
0
3
Order By: Relevance
“…Selected articles and references are provided in Refs. [5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21].…”
Section: Managing Time and Latencymentioning
confidence: 99%
“…Selected articles and references are provided in Refs. [5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21].…”
Section: Managing Time and Latencymentioning
confidence: 99%
“…Both Puschner and Burns [12], and Wilhelm et al [20] give a broad overview of the WCET research. Nevertheless, not all these achievements can be applied to multiprocessor systems.…”
Section: Related Workmentioning
confidence: 99%
“…It is the time a process could eventually need to execute under worst conditions on a given processor. In [20], Wilhelm et al define the goal of WCET analysis concerning the upper bounds of the execution time:…”
mentioning
confidence: 99%
“…cache misses) and 3) estimate calculation; see [23] for a survey of techniques and tools. Sound estimate calculation computes an upper bound of all execution times of a whole program (i.e.…”
Section: Introductionmentioning
confidence: 99%