|SPARC references email@example.com (1991-03-20)|
|Re: SPARC references firstname.lastname@example.org (1991-03-24)|
|Re: SPARC references email@example.com (John ffitch) (1991-03-28)|
|Re: SPARC references firstname.lastname@example.org (1991-03-29)|
|Re: SPARC references chased@Eng.Sun.COM (1991-04-01)|
|Re: SPARC references email@example.com (1991-04-01)|
|Re: SPARC references firstname.lastname@example.org (1991-04-12)|
|From:||email@example.com (David Keppel)|
|Keywords:||SPARC, optimize, code|
|Organization:||Computer Science & Engineering, U. of Washington, Seattle|
|References:||<1991Mar20.firstname.lastname@example.org> <1991Mar24.email@example.com> <1991Mar28.firstname.lastname@example.org> <1991Mar29.email@example.com>|
|Date:||Mon, 1 Apr 91 17:42:02 GMT|
>John ffitch <firstname.lastname@example.org> 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' (184.108.40.206) in
;-D on ( SPARC dereferences, too! ) Pardo
Return to the
Search the comp.compilers archives again.