scispace - formally typeset
P

Peter Puschner

Researcher at Vienna University of Technology

Publications -  139
Citations -  5751

Peter Puschner is an academic researcher from Vienna University of Technology. The author has contributed to research in topics: Worst-case execution time & Code generation. The author has an hindex of 32, co-authored 137 publications receiving 5474 citations. Previous affiliations of Peter Puschner include University of Vienna & Information Technology University.

Papers
More filters
Proceedings ArticleDOI

A Tool for the Computation of Worst Case Task Execution Times

TL;DR: A new task taming analysis tool for MARS that not only allows to compute worst case execution time bounds of high quality but also produces detailed information about the extent to which every statement contributes to this bound and allows to experiment with hypothetical times.
Book ChapterDOI

Time-predictable computing

TL;DR: This paper proposes a universal definition of time-predictability that combines the essence of different discussions about this term and is instantiated to concrete types ofTime-p Predictability, like worst-case execution time (WCET) predictability.

On Composable System Timing, Task Timing, and WCET Analysis

TL;DR: The source of complexity in today’s embedded systems is described in terms of mechanisms and side effects that determine variations in the timing of single tasks and entire applications and strategies to reduce the complexity are proposed.
Journal ArticleDOI

Transforming flow information during code optimization for timing analysis

TL;DR: This article presents a method for transforming flow information from source code to machine code in parallel to code transformations performed by an optimizing compiler and shows that it can be applied to every type of semantics-preserving code transformation.
Proceedings ArticleDOI

Java virtual-machine support for portable worst-case execution-time analysis

TL;DR: This paper proposes a framework for providing portableWCET analysis for the Java platform by separating the WCET analysis process in three stages and by analysing the Java byte code, not the high-level source code, thus enabling the analysis of programs written in other languages.