Sweet, looking forward to see it, I made new commits yesterday, with debugging info added in. Helps us know how far we have got and where exactly the error is, as development is not consistently going on at the moment. when you commit vex, please do ensure that the changes dont back out each other. Looking forward to the new vex :) Hopefully that will fix our problems. I was debugging run_innerloop asm before I slept off at some point. Regards, Kailash
On 11/8/05, Eric Auge <[EMAIL PROTECTED]> wrote: > Hello, > > FYI VEX seems to be on the "good" way, still some issue in > m_translate.c and some other places, but they doesn't > look like big blocking issues :) > > I was unable to finish yesterday night, > I hope to finish tonight. > > see ya guys, > Regards, > > Eric > > NB: > 01:23AM <hsaliak> eh run_innerloop is pushing registers into stack > 01:24AM <hsaliak> doh nevermidn > 01:25AM <hsaliak> l8r > 01:25AM <hsaliak> we should discuss on ML more > <spoty> yes > <spoty> run_innerloop is pusshin register on the stack > <spoty> because that's what require VEX > <spoty> it is doing the VEX exec environnement setup > <spoty> iirc > > _______________________________________________ > Vg4nbsd-devel mailing list > [email protected] > http://lists.berlios.de/mailman/listinfo/vg4nbsd-devel > _______________________________________________ Vg4nbsd-devel mailing list [email protected] http://lists.berlios.de/mailman/listinfo/vg4nbsd-devel
