Newsgroups: comp.archives
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!ox.com!msen.com!emv
From: pardo@cs.washington.edu (David Keppel)
Subject: [compilers] Re: SPARC references
Message-ID: <1991Apr3.070055.10800@ox.com>
Followup-To: comp.compilers
Keywords: SPARC, optimize, code
Sender: emv@msen.com (Edward Vielmetti, MSEN)
Reply-To: pardo@cs.washington.edu (David Keppel)
Organization: Computer Science & Engineering, U. of Washington, Seattle
References: <1991Mar20.222801.11711@cs.cornell.edu> <1991Mar24.222923.10183@ccu.umanitoba.ca> <1991Mar28.115715.3545@maths.bath.ac.uk> <1991Mar29.214751.3045@ccu.umanitoba.ca> <1991Apr1.174202.1976@beaver.cs.washington.edu>
Date: Wed, 3 Apr 1991 07:00:55 GMT
Approved: emv@msen.com (Edward Vielmetti, MSEN)
X-Original-Newsgroups: comp.compilers

Archive-name: sys/sparc/pardo-sparc-stack/1991-04-01
Archive: cs.washington.edu:/pub/pardo/README.SPARC [128.95.1.4]
Original-posting-by: pardo@cs.washington.edu (David Keppel)
Original-subject: Re: SPARC references
Reposted-by: emv@msen.com (Edward Vielmetti, MSEN)

>John ffitch <jpff@maths.bath.ac.uk> writes:
>>[Somebody's trampling the stack, and honest, it isn't me!]

Back when I was trying to port a threads package to the SPARC I had an
opportunity to learn all about the stack layout conventions.  I wrote up
my experience, which is mostly concerned with the interaction between
register windows and stack layout.  Nonetheless, it might prove
instructive for anybody who's interested in the stack layout.

For the next two weeks or so, you can get a copy of my ``what I learned''
writeup via anonymous ftp from `cs.washington.edu' (128.95.1.4) in
`pub/pardo/README.SPARC'.  

	;-D on  ( SPARC dereferences, too! )  Pardo
-- 
Send compilers articles to compilers@iecc.cambridge.ma.us or
{ima | spdcc | world}!iecc!compilers.  Meta-mail to compilers-request.