Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| SPARC references ressler@cs.cornell.edu (1991-03-20) |
| Re: SPARC references salomon@ccu.umanitoba.ca (1991-03-24) |
| Re: SPARC references jpff@maths.bath.ac.uk (John ffitch) (1991-03-28) |
| Re: SPARC references salomon@ccu.umanitoba.ca (1991-03-29) |
| Re: SPARC references chased@Eng.Sun.COM (1991-04-01) |
| Re: SPARC references pardo@cs.washington.edu (1991-04-01) |
| Re: SPARC references torek@elf.ee.lbl.gov (1991-04-12) |
| Newsgroups: | comp.compilers |
| From: | pardo@cs.washington.edu (David Keppel) |
| Keywords: | SPARC, optimize, code |
| 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> |
| Date: | Mon, 1 Apr 91 17:42:02 GMT |
>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
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.