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: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Stack and Heap sizes
Date: 1997/04/18
Message-ID: <dewar.861363791@merv>#1/1
X-Deja-AN: 235701272
References: <335358C5.43F8@reading.ac.uk> <33548420.1046@reading.ac.uk>
 <3354B65D.124@reading.ac.uk>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-04-18T00:00:00+00:00
List-Id: <comp.lang.ada>


W P Berriss asks

<<A few quick questions.

Is there a limit that GNAT imposes on the size of the
stack or heap available to the main program or
on an object (such as an array)?

Is there a compiler option to alter the limit?

Is there a way to find out what the limit is
at a given time (say on a 2Gbyte RAM machine?)>>

GNAT imposes no limit on the stack or heap available to the main program

There is no compiler option to alter the limit, since this is an
operating system issue. Many operating systems do have mechanisms for
adjusting the stack size (you did not even say what system you were
using).

Again, finding out the limit is an operating system issue. It is unlikely
that the sioze depends on how much RAM you have.