|
From: Nicholas N. <nj...@cs...> - 2005-02-15 00:49:36
|
On Mon, 14 Feb 2005, Julian Seward wrote: > There's been a lot of development work on V recently, not all of > it visible. Jeremy has improved the threading situation by finally > allowing V to run thread libraries natively, which is a great > simplification. I'm working on "Vex", an architecture-neutral > replacement for the UCode framework which facilitates porting > V away from x86. > > It has been a good six months since 2.2 was released and it's > now way overdue for another stable release. Many bugs have been > fixed, and the new threading stuff really ought to go live sooner > rather than later. So we will do a 2.4 release, hopefully > within the next month. Jeremy is in charge of stabilising the > tree to a point where it is at releasable quality. > > 2.4 will be the last x86-only valgrind, and the last using the > UCode framework. Future valgrinds will be built on Vex, a new > library for dynamic translation and instrumentation. Vex is now > working well for x86, and amd64 support is starting to work. > > I will be merging the current cvs tree and the vex development > tree. The aim will be to release an alpha grade "technology > demonstrator" as soon as amd64-linux support is usable. We will > then push towards stabilising the tree for a mid-year valgrind-3.0 > release, which should provide Linux support for x86, amd64, and > possibly ppc32, all from a unified code base. I think this is all great. Big kudos to Julian and Jeremy for these two strands of work, which should improve Valgrind's future viability (via Vex) and correctness/maintainability/stability (via native pthreads) no end. Big ongoing thanks to Tom also for his tireless bug-fixing. I think it's going to be a good year for Valgrind :) N |