fill_params GCI task

Patrick R. Michaud pmichaud at
Fri Jan 7 15:35:02 UTC 2011

On Fri, Jan 07, 2011 at 04:15:14PM +0100, Nick Wellnhofer wrote:
> I completely agree with your analysis. There's another approach:
> (4) We don't build the signature object at all, but we transfer the
> arguments directly from the "raw" signatures and the registers of
> the caller to the registers of the callee. So we'd have a single
> function that does the work of build_sig_object and fill_params.
> This might be even more complex than fill_params, though.

Isn't "transfer arguments directly to registers of callee"
almost _exactly_ what we had before the work on the new Parrot
calling conventions work of ~16 months ago...?


More information about the parrot-dev mailing list