Dan Sugalski <[EMAIL PROTECTED]> wrote:
Okay, aesthetics and making up for a flaw in the implementation of how IMCC tracks opcodes and registers.
That flaw is caused by the assymmetry of opcodes, or by indirect register usage if opcodes like bare C<invoke>. But as that shall not be fixed now, lets' keep all these ugly hacks.
It's so nice to see that any design element you don't approve of is referred to in such glowing terms...
Regardless, now that this matter's closed it's time to get other stuff going. Tail calls, for one.
> Neither of those are sufficient, individually or together.
Your code is spilling ... ;)
Well, duh. I've got a single sub with over a meg of source and 20k+ explicit temps. Of *course* it's going to make the register coloring algorithm scream. While the coloring and spilling code needs help, feeding it naively generated code is part of the problem.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
