• Documents
  • Authors
  • Tables
  • Other Seers ▼
    RefSeer AckSeer CollabSeer SeerSeer
  • Log in
  • Sign up
  • MetaCart

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations | Disambiguate

Automatic Utilization of Constraints for Timing Analysis (1999)

by C Healy
Add To MetaCart

Tools

Sorted by:
Results 1 - 3 of 3

A Tool for Automatic Flow Analysis of C-programs for WCET Calculation

by Jan Gustafsson, Björn Lisper, Christer Sandberg, Christer S, Nerina Bermudo - In 8 th IEEE International Workshop on Object-oriented Real-time Dependable Systems (WORDS 2003 , 2003
"... interpr. ..."
Abstract - Cited by 9 (2 self) - Add to MetaCart
Abstract not found

Generalizing Parametric Timing Analysis

by Joel Coffman, Christopher Healy, Frank Mueller, David Whalley
"... In the design of real-time and embedded systems, it is important to establish a bound on the worst-case execution time (WCET) of programs to assure via schedulability analysis that deadlines are not missed. Static WCET analysis is performed by a timing analysis tool. This paper describes novel impro ..."
Abstract - Cited by 2 (0 self) - Add to MetaCart
In the design of real-time and embedded systems, it is important to establish a bound on the worst-case execution time (WCET) of programs to assure via schedulability analysis that deadlines are not missed. Static WCET analysis is performed by a timing analysis tool. This paper describes novel improvements to such a tool, allowing parametric timing analysis to be performed. Parametric timing analyzers receive an upper bound on the number of loop iterations in terms of an expression which is used to create a parametric formula. This parametric formula is later evaluated to determine the WCET based on input values only known at runtime. Effecting a transformation from a numeric to a parametric timing analyzer requires two innovations: 1) a summation solver capable of summation non-constant expressions and 2) a polynomial data structure which can replace integers as the basis for all calculations. Both additions permit other methods of analysis (e.g. caching, pipeline, constraint) to occur simultaneously. Combining these techniques allows our tool to statically bound the WCET for a larger class of benchmarks.

Improvements Of The Flow Analysis in WCET Tools

by Christer Sandberg , 2005
"... The worst case execution times, the WCET, are often essential to know for tasks that have to fulfill deadlines. Such tasks can often be found in real time systems. In order to calculate the WCET, flow constraints, like maximum iterations of loops, needs to be known. Entering all such flow constraint ..."
Abstract - Add to MetaCart
The worst case execution times, the WCET, are often essential to know for tasks that have to fulfill deadlines. Such tasks can often be found in real time systems. In order to calculate the WCET, flow constraints, like maximum iterations of loops, needs to be known. Entering all such flow constraints to a WCET tool require a lot of work for the user to be done. Therefore methods for achieving flow constraints automatically are important. However, most of today 's WCET tools require manual annotations of loops for real sized programs. One of the reasons is that the most powerful analysis methods are too costly in terms of computation power. This paper
The National Science Foundation
  • About CiteSeerX
  • Submit Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2010 The Pennsylvania State University