This was directly from XaAES, where no libc16 is required, as you might know.My question is still valid. Where does the linker find the implementation of vsprintf() ?
This is libkern (where everything is short).
It is not about the 000 version of XaAES... but the CPU on which you run it. ARAnyM emulates a 68040. If it would be possible to run XaAES on 68000, it would crash with 3 bombs when some some variable appears at an odd address.
Someone should test this.
The inlined code isn't used - at least for VDI, and XaAES doesn't do any AES-traps AFAIK. The code that's used does only backup one reg, I think.Why is the code not used ?
You are right: It is used. I just started the ozk-XaAES (which uses current libgem) and pixel-detection fails, so this is not it. But I will update my gemlib.
Where do you know the 62MB? And the same runs on a TT with 24MB or similar.The FastRAM starts at 0x01000000. vdi_intin is at 0x04EB850B. (0x04EB850B - 0x01000000) / 1024 / 1024 = 62.72Well, It may not be wrong, maybe XaAES puts the stack very high in the FastRAM... I don't know the MiNT memory layout, but this is surprising.
Me neither. -- Helmut Karlowski