Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cuae2!gatech!lll-lcc!seismo!rochester!ken
From: ken@rochester.UUCP
Newsgroups: comp.os.minix
Subject: Re: Stack growth
Message-ID: <24830@rochester.ARPA>
Date: Sat, 14-Feb-87 05:13:37 EST
Article-I.D.: rocheste.24830
Posted: Sat Feb 14 05:13:37 1987
Date-Received: Sun, 15-Feb-87 00:23:09 EST
References: <966@ulowell.cs.ulowell.edu> <1565@cit-vax.Caltech.Edu> <1377@cbmvax.cbmvax.cbm.UUCP> <800@vaxb.calgary.UUCP>
Reply-To: ken@rochester.UUCP (SKY)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 15
Keywords: stacks

|OK, I'll bite. I've always thought that stacks grow down from the top of
|memory because it's more satisfying to always have the first byte of the
|program in a fixed location (say 0) than to have the first byte of the
|*stack* always in a fixed location.
|
|For example, on a stand-alone PDP 11, the stack grows down from the top of
|memory, *wherever that may be*. The program is loaded into low memory, which
|is always the same place. So you don't have to re-link all your programs
|when you buy more memory.

This isn't true in RT-11. The stack grows toward low memory, but from the
default location of 1000 octal. So if your Whitesmiths C program used a lot
of stack you had to move the start address up to make room.

	Ken