From: Stuart Palin <stuart.palin@baesystems.com>
Subject: Re: Worst Case Execution Time Tool?
Date: Wed, 05 Dec 2001 17:32:42 +0000
Date: 2001-12-05T17:32:42+00:00 [thread overview]
Message-ID: <3C0E5A3A.B5C835A6@baesystems.com> (raw)
In-Reply-To: 3C0E3535.58437022@computer.org
StationSteve wrote:
<snip>
> So how (or do?) people typically PROVE that their program will actually meet their deadlines? If
> somebody does a rate monotonic design, they have to assume the execution time of task. How does one
> determine the true execution time so that the design can be shown to be correct?
On several projects we have used [in-house] WCET tools, our most recent
being for a MC68020/MC68882 target with code generated by the XD-Ada
compiler.
Unfortunately this does not help you (not a commercially available tool
and not '386).
--
Stuart Palin
Principal Software Engineer
BAE SYSTEMS Avionics Ltd, Rochester
G-NET 791 3364 mailto:stuart.palin@baesystems.com
prev parent reply other threads:[~2001-12-05 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 22:51 Worst Case Execution Time Tool? StationSteve
2001-12-05 0:10 ` Ted Dennison
2001-12-05 17:28 ` Stuart Palin
2001-12-05 18:33 ` Ted Dennison
2001-12-06 14:05 ` StationSteve
2001-12-06 16:40 ` Ted Dennison
2001-12-06 21:27 ` StationSteve
2001-12-06 22:44 ` Ted Dennison
2001-12-07 1:00 ` annonymous
2001-12-05 10:00 ` Rod Chapman
2001-12-05 14:54 ` StationSteve
2001-12-05 15:31 ` Jeffrey L. Susanj
2001-12-05 17:32 ` Stuart Palin [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox