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

  • Authors:
  • Björn Lisper;Andreas Ermedahl;Dietmar Schreiner;Jens Knoop;Peter Gliwa

  • Affiliations:
  • School of Innovation, Design, and Engineering, Mälardalen University, Västerås, Sweden;School of Innovation, Design, and Engineering, Mälardalen University, Västerås, Sweden;Institute of Computer Languages, Vienna University of Technology, Vienna, Austria;Institute of Computer Languages, Vienna University of Technology, Vienna, Austria;GLIWA GmbH embedded systems, München, Germany

  • Venue:
  • ISoLA'10 Proceedings of the 4th international conference on Leveraging applications of formal methods, verification, and validation - Volume Part II
  • Year:
  • 2010

Quantified Score

Hi-index 0.00

Visualization

Abstract

Code-level timing analysis, such as Worst-Case Execution Time (WCET) analysis, takes place at the binary level. However, much information that is 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, different source-level analyses can provide valuable support for timing analysis. However, source-level analysis is not always smoothly applicable in industrial projects. In this paper we report on the experiences of applying source-level analysis to industrial code in the ALL-TIMES FP7 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.