Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!world!iecc!compilers-sender From: pardo@cs.washington.edu (David Keppel) Newsgroups: comp.compilers Subject: Re: SPARC references Keywords: SPARC, optimize, code Message-ID: <1991Apr1.174202.1976@beaver.cs.washington.edu> Date: 1 Apr 91 17:42:02 GMT Article-I.D.: beaver.1991Apr1.174202.1976 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> Sender: compilers-sender@iecc.cambridge.ma.us Reply-To: pardo@cs.washington.edu (David Keppel) Organization: Computer Science & Engineering, U. of Washington, Seattle Lines: 17 Approved: compilers@iecc.cambridge.ma.us >John ffitch 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.