Re: Unboxed float arguments

On 6/22/12 12:32 AM, Helmut Eller wrote:
> * Raymond Toy [2012-06-22 04:36] writes:
>
>>> I could use a bit of feedback regarding the names.  Currently I use
>>> "typed calling convention" resp. "typed entry point" and for the regular
>>> entry point I use "external entry point" or XEP.  For the :typed-no-xep
>>> case the naming is a bit misleading as the typed entry point is the only
>>> entry point and in the IR has the lambda-kind set to :external, i.e. the
>>> XEP is a typed entry.  Is there a better word for it?
>> Sorry that I still haven't had a chance to look at your code or even
>> play with it.
>>
>> I find the :typed and :typed-no-xep hard to remember, though.  Could it
>> be :unboxed instead?  That makes it pretty clear that you're using
>> calling convention that supports unboxed args.
> The only issue I have with "unboxed" is that the calling convention also
> supports boxed values, e.g. arrays, for which the type check was already
> done in the caller.

That's true, but I don't think anyone expects unboxed arrays.  I find
"typed" confusing because everything has a type.  Maybe acl's
immediate-arg is better?  But cmucl already has a concept of immediates,
so this can be confusing too.

So, how do I build your changes?  I assume can just do a normal
cross-compile using tccxboot.lisp?

Ray

_______________________________________________
cmucl-imp mailing list
[email protected]
http://lists.zs64.net/mailman/listinfo/cmucl-imp