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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6be476fd23132bb7 X-Google-Attributes: gid103376,public From: Samuel Tardieu Subject: Re: Stack and Heap sizes Date: 1997/04/16 Message-ID: #1/1 X-Deja-AN: 235181703 Sender: tardieu@esmeralda.enst.fr References: <335358C5.43F8@reading.ac.uk> <33548420.1046@reading.ac.uk> <3354B65D.124@reading.ac.uk> Mail-Copies-To: sam@ada.eu.org To: William Paul Berriss Organization: TELECOM Paris Newsgroups: comp.lang.ada Date: 1997-04-16T00:00:00+00:00 List-Id: >>>>> "William" == William Paul Berriss writes: William> Is there a limit that GNAT imposes on the size of the stack William> or heap available to the main program or on an object (such William> as an array)? No. The stack for the elaboration task (the one which does all the elaborations and then calls the main program) can grow as long as there is enough memory (it depends on your hardware and OS). Same for heap if you use the default storage pool. It is different for other tasks, where a pragma Storage_Size may be specified to change the default stack size. Sam -- Samuel Tardieu -- sam@ada.eu.org