From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00,TO_NO_BRKTS_FROM_MSSP autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ba6120170d8e7faf X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-12-04 16:10:52 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!news.maxwell.syr.edu!out.nntp.be!propagator-SanJose!in.nntp.be!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Ted Dennison References: <3C0D536C.2E059EE8@computer.org> Subject: Re: Worst Case Execution Time Tool? Message-ID: <0CdP7.48989$xS6.81382@www.newsranger.com> X-Abuse-Info: When contacting newsranger.com regarding abuse please X-Abuse-Info: forward the entire news article including headers or X-Abuse-Info: else we will not be able to process your request X-Complaints-To: abuse@newsranger.com NNTP-Posting-Date: Tue, 04 Dec 2001 19:10:36 EST Organization: http://www.newsranger.com Date: Wed, 05 Dec 2001 00:10:36 GMT Xref: archiver1.google.com comp.lang.ada:17421 Date: 2001-12-05T00:10:36+00:00 List-Id: In article <3C0D536C.2E059EE8@computer.org>, StationSteve says... > >Are there any tools that quantitatively determine the worst case >execution time (WCET) of an Ada83 program or subprogram? Execution >platform is Intel 80386SX bare machine. I think I'm looking for >something similar to SPARK Examiner's WCET analysis, but for Ada83. Wouldn't such a tool also be able to solve the Halting Problem? ( http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=halting+problem ) --- T.E.D. homepage - http://www.telepath.com/dennison/Ted/TED.html No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced.