Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!versatc!mips!earl@orac.mips.com
From: earl@orac.mips.com (Earl Killian)
Newsgroups: comp.arch
Subject: Re: Register usage
Message-ID: <20810@orac.mips.COM>
Date: 31 May 89 22:46:25 GMT
References: <259@mindlink.uucp> <25382@ames.arc.nasa.gov> <m0fRx4x-0001fDC@mipon2.intel.com> <1RcY6x#64Zq3Y=news@anise.acc.com> <26204@ames.arc.nasa.gov>
Sender: earl@mips.COM
Reply-To: earl@orac.mips.com (Earl Killian)
Organization: MIPS Computer Systems Inc.
Lines: 11
In-reply-to: lamaster@ames.arc.nasa.gov (Hugh LaMaster)

Another problem with register windows is that they make it difficult
to support coroutines.  I typically do queuing simulations by having
multiple coroutines representing separate entities, each with a
separate stack.  I've implemented this on VAXs, 68000s, and MIPS boxes
with only 20-50 lines of assemlber.  But I can't see any way to do
stack switching on a register window machine without a kernel call
(yuck).  Have any of the register window architectures implemented a
way for user code to do stack switching?
--
UUCP: {ames,decwrl}!mips!earl
USPS: MIPS Computer Systems, 930 Arques Ave, Sunnyvale CA, 94086