🚀 go-pugleaf

[ To reread the original article, use ^P in rn (is this hypertext?) ]

>Can anyone confirm/deny this hunch for me, or better yet tell me exactly 
>how parameters are handled?
>

Exec does not concern itself with the parameters, the mechanism by which
they are passed to the library is purely a convention between the 
assembler routine that you link with and the .library.  Traditionally,
the assembler routine takes the parameters off the stack (where they
were put when you called it from your C code) and puts them into the
registers the .library code is expecting them in (at the back of the
Exec RKM you can find the specifications for 1.1 library functions).
Another convention is that pointers should be passed in address registers,
everything else in data registers, but this isn't always followed (e.g.
dos.library).  Both these conventions were adopted, I presume, to optimize
the speed potential of the library code.

You can, however, define your own convention for passing arguments to your
.library.  If you are writing the .library in C, it may be convenient to decree
that all arguments will be passed on the stack.  Your assembler routine would
then only need to 'JMP' (not 'JSR') to the appropriate .library
vector.  That library vector could then 'JMP' directly to your .library
function written in C.  This avoids the wastage of time (and space) needlessly
taking parameters from the stack and putting them in registers only to push
the register values back on the stack again.

It would be nice if the Lattice C '#pragma libcall' feature would support this
method of passing parameters, as it currently only supports the pass-in-register
model (which is, admittedly, adequate for the system libraries).

--
Jeff Kelley    Graphics Lab, Dept. of Computer Science, University of Waterloo
   uunet!watmath!watcgl!jvkelley  	tel:   (519) 578-4514
"Remember, this is not a competition, only an exhibition. Please, no wagering."
	- David Letterman