Re: [Valgrind-developers] 3.0.0 and after

[Nicholas N. <nj...@cs...>]

On Mon, 8 Aug 2005, Julian Seward wrote:

> I'd like to do a 3.0.1 relatively soon, to fix easily-fixed
> breakage in 3.0.0.

Sounds good.

> - A rewritten address space manager, which will finally make
>  the thing work properly on 64-bit platforms, and should
>  provide a better base for porting to non-Linux OSs.

Yes!  A lot of the outstanding problems and bugs are related to this.

> - reinstate, or delete, Addrcheck.  This could involve a
>  study of the compressed-Vbit-representation problem.
>
> - review the thread-modelling stuff, so that at a minimum the
>  pthread-API-abuse checks can be reinstated, and, ultimately,
>  Helgrind can be fixed up.

Both would be good, I think it will come down to whether anyone has time 
to look at them;  they're both sizeable projects.

> I'd like to have 3.1.0 out within the next three months if that
> proves viable.  Taking (another) leaf from the Gcc Way Of Doing
> Things, that would mean at most 2 months of new feature hacking
> followed by a 1-month stabilisation period.

Also sounds good.

> Generally speaking, as we move on from 3.0, the emphasis changes
> from dealing with different instruction sets to making the system
> level simulation more portable, so as to improve the possibility
> of porting away from Linux.  A side effect of that is to continue
> the modularisation/restructuring of the code base that started
> a couple of months back.

Again, yes, sounds good.

N