Measurement-Based Worst-Case Execution Time Analysis

Wenzel, Ingomar; Kirner, Raimund; Rieder, Bernhard; Puschner, Peter

doi:10.1109/seus.2005.12

Cited by 45 publications

(23 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To approach a full subpath coverage within each program segment, a formal test-data generation method based on model checking is used [WRKP05a,WRKP05b]. However, to compensate the high computation cost of formal test-data generation, a three-step approach is used:…”

Section: Employed Methodsmentioning

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.

1,460

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: Employed Methodsmentioning

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.

1,460

1,029

View full text Add to dashboard Cite

show abstract

“…MTime is a research prototype from the Real-Time Systems Group at Vienna University of Technology (TUVienna) [42] and [41]. MTime supports the processor Motorola HCS12 [15] with the COSMIC compiler [8].…”

Section: Mtimementioning

confidence: 99%

The worst-case execution time tool challenge 2006

Tan

2009

Int J Softw Tools Technol Transfer

View full text Add to dashboard Cite

The first international Worst Case Execution Time (WCET) Tool Challenge in 2006 used benchmark programs to evaluate academic and commercial WCET tools. It aimed to study the state-of-the-art in WCET analysis. The WCET Tool Challenge comprised two parallel evaluation approaches: an internal evaluation by the respective tool developers and an external test by a neutral person of an independent institute. The latter was conducted by the author of this paper. Focusing on the external test, we describe the rules, benchmarks, participants and discuss the obtained results.

show abstract

“…Symbolic execution requires a high implementation effort and therefore does not meet the requirements. Model checking was used within the MoDECs project [8] to generate test data and identify infeasible paths where it proved to be an efficient replacement for a custom symbolic execution engine. Since the CBMC model checker provides good performance and an ANSI-C interface a method has been developed to calculate loop bounds using CBMC.…”

Section: The Model Checking Approachmentioning

confidence: 99%

“…During the MoDECs project [8] we examined medium to large industrial embedded applications using the CBMC model checker and did not encounter any problems like exorbitant memory usage or execution times related to the code size of the applications. Therefore it can be assumed that the proposed approach will work for applications of the same size as well, even if they contain loops.…”

Section: Figure 1 Resource Consumption Over Iterationsmentioning

confidence: 99%