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_05,INVALID_DATE, MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4 Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!sundc!hadron!inco!holt From: holt@inco.UUCP (Mark Holt) Newsgroups: comp.lang.ada Subject: RFI: Predicting memory requirements for ADA tasks Message-ID: <433@inco.UUCP> Date: Mon, 28-Sep-87 08:18:12 EDT Article-I.D.: inco.433 Posted: Mon Sep 28 08:18:12 1987 Date-Received: Tue, 29-Sep-87 06:27:16 EDT Organization: McDonnell Douglas-INCO, McLean, VA Keywords: ADA, memory, predicting, help List-Id: I am posting this for Judith Klein and Bryan Wolf, McDonnell Douglas - Inco, Inc. ---Begin-- We are looking for an existing, or a way of developing a, predictor model for the amount of memory required to store the code being developed. We are developing our code on MVS using the Intermetrics compiler (currently version 5.4), however, any information on the same subject, even if in a different environment, might prove to be useful. In other words, given: a) estimated sloc count b) estimated size of retained data in bytes c) estimated size of interface objects, how much memory do we require in addition to the Run Time System (RTS)? Are there constructs that are more/less efficient storage wise and performance wise? (e.g. is an IF-THEN-ELSE better than a CASE statement in some cases?) ----End-- Thanx, -- /*--------------------------------------------------------------* * Mark L Holt * * McDonnell Douglas - Inco, Inc. * * ...!seismo!sundc!hadron!inco!holt * * "If you ain't the lead dog, the scenery never changes" * * DISCLAIMER: The opinions expressed are my own and in no way * * reflect the views of McDonnell Douglas or its subsidiaries. * *--------------------------------------------------------------*/