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,e5eb8ca5dcea2827 X-Google-Attributes: gid103376,public From: Tucker Taft Subject: Re: Ada OO Mechanism Date: 1999/06/09 Message-ID: <375E9424.3A8E748@averstar.com>#1/1 X-Deja-AN: 487546476 Content-Transfer-Encoding: 7bit Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.burl.averstar.com References: <7i05aq$rgl$1@news.orbitworld.net> <7i17gj$1u1k@news2.newsguy.com> <7icgkg$k4q$1@nnrp1.deja.com> <3749E9EC.2842436A@aasaa.ofe.org> <7id2eo$fag@drn.newsguy.com> <3749FF7D.F17CE16A@aasaa.ofe.org> <374AC676.F7AE0772@lmco.com> <7ieuja$5v9@news1.newsguy.com> <7ifd6l$bmf@sjx-ixn1.ix.netcom.com> <1999Jun9.070724.1@eisner> Content-Type: text/plain; charset=us-ascii Organization: AverStar (formerly Intermetrics) Burlington, MA USA Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-06-09T00:00:00+00:00 List-Id: Larry Kilgallen wrote: > > Reply-To: Kilgallen@eisner.decus.org.nospam > Organization: LJK Software > Lines: 14 > > In article <375D9A3D.E1CCCC63@averstar.com>, Tucker Taft writes: > > > Several compilers use what is called a "secondary stack" (or a "data stack"), > > as distinct from the "primary stack" (or "control stack"). > > The secondary stack is generally managed in a mark/release manner. > > There is one per task. > > So in such compilers, how does specification of task (stack) size > relate to the primary and/or secondary stack ? It varies. In some, it is the sum of the space given to the primary and secondary stack, which "grow" toward each other. In others, it only controls the primary stack, and the secondary stack is represented as an arbitrarily extendable linked-list of large chunks. There are probably other combinations as well. > Do any compilers that use this method also support unlimited (well, > at least unspecified) stack size for the main task ? For both stacks ? I would guess that many compilers that run on Unix-like timesharing systems use the automatic stack extension feature to handle the main primary stack, and either have a fixed size for the secondary stack, or represent the secondary stack using chunks and have no fixed limit. On most embedded systems, I suspect that the main task's primary and secondary stack sizes are set at link-time. > Larry Kilgallen -- -Tucker Taft stt@averstar.com http://www.averstar.com/~stt/ Technical Director, Distributed IT Solutions (www.averstar.com/tools) AverStar (formerly Intermetrics, Inc.) Burlington, MA USA