[Chicken-hackers] ABI woes

2015-07-10 Thread felix . winkelmann
Hello! After thinking about this, it seems to be that the "compound literal" approach is the best one. What this means is that CPS-calls are changed in such a manner, that arguments are passed rthrough a pointer to a C_word-array (so it doesn't have to do anything with compound literals, that w

[Chicken-hackers] ABI woes

2015-07-10 Thread felix . winkelmann
> > - There is no need for "rest-arg wrappers", functions that extract the rest > > argument and then call the actual compiled C function. This can be done > > directly from the argvector. > > This is cool, but if I understand correctly it also means that all the > C_fast_retrieve_proc(lf[123]

[Chicken-hackers] ABI woes

2015-07-11 Thread felix . winkelmann
> > > On Jul 10, 2015, at 13:23, felix.winkelm...@bevuta.com wrote: > > > > The problem with other approaches (own implementation of varargs, using > > assembly for forcing some sort of generic call, etc.) is that they are > > provisional hacks and take at least as much time to implement as

Re: [Chicken-hackers] ABI woes

2015-07-10 Thread Peter Bex
On Fri, Jul 10, 2015 at 12:23:36PM +0200, felix.winkelm...@bevuta.com wrote: > Hello! > > After thinking about this, it seems to be that the "compound literal" > approach > is the best one. What this means is that CPS-calls are changed in such a > manner, that arguments are passed rthrough a po

Re: [Chicken-hackers] ABI woes

2015-07-11 Thread Oleg Kolosov
> On Jul 10, 2015, at 13:23, felix.winkelm...@bevuta.com wrote: > > The problem with other approaches (own implementation of varargs, using > assembly for forcing some sort of generic call, etc.) is that they are > provisional hacks and take at least as much time to implement as the cleaner