Hello Kjell,
Saturday, August 23, 2008, 5:44:08 PM, you wrote:
First of all, I'm learning about all that myself, so my answers might
not be necessary correct (I hope someone will correct me if I'm
wrong).
Okay I want to compile it on cygwin.
Which version of fonc should I use?
This one is a
Has anybody started on an (x86) 64-bit port of the code generator? I
would like to collaborate if someone is working on this.
I'd identified that as my next fonc-related task, but haven't really
started on it, and may not get a chance to work on it in the next couple
of weeks. But if you do
Okay I want to compile it on cygwin.
Which version of fonc should I use?
What is Jolt? What is Coke? What is Pepsi? Cola is Lisp
plus Smalltalk right? Plus a lot of weird stuff like variables
that are macros and weird stuff like that.
Is there a debugger I can use to step through its execution?
Currently, libid and idc only support 1 tag: fixnum or allocated object. All
fixnums in idc and above require masking and shifting before operations. A
fixnum operation heavy program, for example, would benefit from using 00 tags,
as in SBCL, unless tags can be optimized away by type
Adrian correctly pointed out that tagging is a time/space trade-off. I did
demonstrate that different processors did perform differently by varying
tagging schemes.
Yes, the current tagging scheme (with 0 as nil) seemed to perform best
in your benchmark. But will it make a difference for
If this was implemented in higher-levels of abstraction we could introduce
different tagging schemes to support locatives, flonums, etc. This could lead
to more language features, reduced memory usage and garbage on smaller
hardware and better performance on 64-bit machines that don't need
If this was implemented in higher-levels of abstraction we could
introduce
different tagging schemes to support locatives, flonums, etc. This could
lead
to more language features, reduced memory usage and garbage on smaller
hardware and better performance on 64-bit machines that don't need
Is anybody interested in adding parameterized word tagging in libid, idc and
up through Jolt?
If this was implemented in higher-levels of abstraction we could introduce
different tagging schemes to support locatives, flonums, etc. This could lead
to more language features, reduced memory
