On 12/2/05, Raymond Toy wrote:
> Do you know what the bugs are? Are the in the bug tracker? That
> would certainly help in fixing the translation code.
the difficulty with the translation code is that it (at present)
amounts to a reimplementation of the interpreter,
which is now out of date.
for each function recognized by the translator,
the translator emits some code, which can run faster
than the interpreted function, but which may or may not
have the same effect. (this is aside from obvious bugs
such as failure to translate or failure to load the translated file.)
for other functions, the translator emits something
generic like MFUNCALL or MEVAL; in that case
the effect is the same as the interpreter, but it is no faster.
i don't know what can be done to ensure that translated
functions have the same effect as interpreted,
and yet run faster. maybe turn some functions like
MEVAL1 into macros, and paste the macro expansion
of (MEVAL1 '(($FOO) $X)) into the translator output?
just guessing.
a data point here -- a few months ago i spent a couple of
hours trying to translate the test suite.
i didn't get far (i couldn't get rtest1.mac translated).
bug reports (there are about 10 of them) are all closed, interestingly enough.
for what it's worth,
robert dodier