Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site spdcc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!spdcc!dyer
From: dyer@spdcc.UUCP (Steve Dyer)
Newsgroups: net.micro.pc,net.unix-wizards
Subject: process stack handling on XENIX-286
Message-ID: <13@spdcc.UUCP>
Date: Thu, 20-Feb-86 02:52:46 EST
Article-I.D.: spdcc.13
Posted: Thu Feb 20 02:52:46 1986
Date-Received: Fri, 21-Feb-86 07:04:15 EST
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 16
Xref: watmath net.micro.pc:7061 net.unix-wizards:16868
Summary: fixed, or dynamically growing???

I'm still a bit confused about how a process grows (or blows) its
stack under XENIX-286.  To be specific, I'm talking about SCO XENIX V
for the PC/AT.  I can understand why an unprotected machine like the
808[86] requires stack to be pre-allocated, but it would seem to me
that the memory protection facilities of the 286 would allow dynamic
stack growth much like the PDP-11 or VAX families.  Nevertheless, the
XENIX documentation still alludes to constructs like
cc -F hex-number-of-stack-size ...
Is this just a cautious remnant of 8086 compatibility, or is this
still necessary when running objects on a 286 machine running XENIX, too.

Thanks,
-- 
Steve Dyer
dyer@harvard.HARVARD.EDU
{bbncca,bbnccv,harvard}!spdcc!dyer