|
From: Julian S. <js...@ac...> - 2005-09-06 10:33:50
|
> Sounds good. I found a kernel switch to disable the Altivec unit,
> so that's not blocking me anymore. The commented-out lwbrx seems
> to work after a small tweak, and a do-nothing mftb works well
> enough for the programs I'm running now.
lwbrx is done, as is mftb{,u}. We tried the do-nothing game for
the x86/amd64 equivalent (rdtsc) and you end up with hangs,
strange long delays, or divisions by zero.
> lswx and stswx are rearing their ugly heads again. I have two
> solutions coded up, but neither is great.
Yeh.
> 2. Use a dirty helper. This is fast, but for memcheck to work
> properly it really needs the "memory touched" size to be
> an expression instead of a constant. I don't know how messy
> this would be to deal with in memcheck.
The problem is that the instrumentation code generated by memcheck
depends on that size -- that is, the number needs to be known at
translation time.
I'll contemplate this.
Let us know of any other insns you need.
J
|