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 http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
- the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
- 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 firstname.lastname@example.org
Extending Optimising Compilation to Support Worst-Case Execution Time Analysis
Raimund Kirner, TU Wien
The calculation of the WCET needs the knowledge of additional control-flow information so-called flow facts. For convenience, it is preferred to specify this information at the source code level. To perform a precise WCET analysis at object code level it is necessary to map the information onto the object code. For precise WCET analysis of programs optimised by the compiler, the flow facts have to be transformed in parallel to the code transformations performed during optimisation. This talk presents a framework to maintain correct flow facts during code optimisation. Previous solutions are either based on matching the debug information with the source code or on logging of only restricted code transformations. The talk presents a novel concept to transform flow information in parallel to the code transformations performed by the compiler. The code transformations are abstracted to their relevant structural changes. From the structural update and the known semantic control-flow information of the performed code transformation, a safe and precise transformation of the flow information is induced. A graphical transformation framework to describe the performed code transformations supports the compiler developer in understanding the required update of flow facts. The abstract representation of the control flow graph allows the modelling of blocks with multiple branching edges which enables the integration of this method into various compilers. The result is a framework that supports high-quality WCET analysis of optimised code.