You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact

Practical experiences of applying source-level WCET flow analysis to industrial code


Björn Lisper, Andreas Ermedahl, Dietmar Schreiner , Peter Gliwa , Jens Knoop

Research group:

Publication Type:

Journal article


International Journal on Software Tools for Technology Transfer






Code-level timing analysis, such as Worst-Case Execution Time (WCET) analysis, usually takes place at the binary level. However, many program properties that are important for the analysis, such as constraints on possible program flows, are easier to derive at the source code level since this code contains much more information. Therefore, various source-level analyses can provide valuable support for timing analysis. However, source-level analysis is not always smoothly applicable in industrial settings. In this paper we report on the experiences of applying source-level analysis to industrial code in the ALL-TIMES project: the promises, the pitfalls, and the workarounds that were developed. We also discuss various approaches to how the difficulties that were encountered can be tackled.


author = {Bj{\"o}rn Lisper and Andreas Ermedahl and Dietmar Schreiner and Peter Gliwa and Jens Knoop},
title = {Practical experiences of applying source-level WCET flow analysis to industrial code},
volume = {15},
number = {1},
pages = {53--63},
month = {February},
year = {2013},
journal = {International Journal on Software Tools for Technology Transfer},
publisher = {Springer},
url = {}