There are some spectacularly annoying things like the stack bias, but those are easy to hide in the assembler (and those are problems with the System V ABI, not SPARC, embedded ABIs ignore them).
There are some spectacularly annoying things like the stack bias, but those are easy to hide in the assembler (and those are problems with the System V ABI, not SPARC, embedded ABIs ignore them).
The offset is chosen odd as to trivially identify 64-bit code in things like register window overflow trap handlers[2].
When I say I prefer some assembly vs. some other assembly, I speak from the perspective of a kernel/compiler writer. Realistically you will never use assembly to write general purpose code. You either target it from a compiler (in which case it better be easier to target), or write some specialized runtime/driver code, in which case it would better have easy to understand semantics and behavior. If you were to write general purpose code in assembly, say write assembly instead of C, an orthogonal CISC architecture would be way easier to write code for. But nobody does that anymore. People only use assembly when they have to (or target it from a compiler) and for that particular case the features of the ISA that matter most are quite different than what a general purpose programmer would want.
SPARC really excels for me because of how easy it is to target and how easy it is for me understand when I am writing runtime code.
I have various SPARC hardware, the most interesting (and the one eventually used for the Go port) being a single-digit serial number S7-2 system[3]
[1] https://docs.oracle.com/cd/E18752_01/html/816-5138/advanced-...
[2] http://src.illumos.org/source/xref/illumos-gate/usr/src/uts/...
50% of servers in my basement data center are SPARC based.