[M3commit] CVS Update: cm3

[Tony Hosking]

Realise also that on modern x86 machines the stack ends up in internal registers anyway.  x86 processors these days don't actually execute x86 instructions... ;-)

So, it may not be such a performance loss simply to push/pop on the machine stack.  Generating simple code is probably better than more complicated code, because the hardware will still do a good job of executing it.


On 6 Feb 2010, at 17:19, Jay Krell wrote:

> CVSROOT:	/usr/cvs
> Changes by:	jkrell at birch.	10/02/06 17:19:41
> 
> Modified files:
> 	cm3/m3-sys/m3back/src/: M3x86.m3 
> 
> Log message:
> 	save all registers that are in use to memory (temporaries on the stack) around int64 helper functions; this is not ideal though in practise, the few times I have looked, it isn't many registers, like one; it is probably reasonable to alter the frontend to generate the code in a different order?