|
From: Nicholas N. <nj...@cs...> - 2005-08-15 13:30:50
|
On Mon, 15 Aug 2005, Julian Seward wrote: > The point of --single-step=yes here was to ensure that the > guest integer registers, at least, were up to date immediately > before each memory reference, so that the stack-extending > segfault handler can work when self-hosting. But single stepping > has a drastic effect on performance. Vex offers a better > solution, which is --vex-iropt-precise-memory-exns=yes. > This constraints optimisation enough to ensure the abovementioned > property whilst still allowing basic blocks to be > arbitrarily long. > > Uh .. so does this mean you have self-hosting working? Nope. A user had mentioned that this regtest was failing for them, so I tried to fix it. I've changed it to use --vex-iropt-precise-memory-exns=yes now. N |