From: Tim R. <ti...@su...> - 2004-04-08 05:23:45
|
Does anyone recall the claimed reason for 'internalising' the method lookup/activation stuff? It seems pretty pointless to me, sitting here staring at it. I feel sure it must be giving the poor C compiler coniptions to have so much cruft in a single loop, probably leading to register allocation indigestion. So far as I can see the only cost to having them external is the internalize/externalize SP/IP code and that's a couple of storage instructions. The only code I can see particularly benefitting from being 'internal' is the quickreturn prims which use internalPop:thenPush: - but changing them to external status would only involve referring to the global SP/IP and IIRC all of us are using the global vars in an array now which speeds that up. Maybe I'll try it out in my copious spare time. tim -- Tim Rowledge, ti...@su..., http://sumeru.stanford.edu/tim Useful random insult:- A Neanderthal brain in a Cro-Magnon body. |