Re: [Valgrind-developers] Next version numbering

[Philippe W. <phi...@sk...>]

On Thu, 2025-05-01 at 09:40 +0200, Paul Floyd via Valgrind-developers wrote:
> Hi all
> 
> I've been wondering whether we should switch to a year based numbering 
> scheme rather than our current semantic versioning. I'm not sure if 
> there will ever be a version 4. Making Valgrind multithreaded would 
> warrant such a change but I can't see that happening.

I did an experimental multithreaded trial some years ago, the prototype could run
the none tool multi-threaded, so valgrind was able to do nothing faster :).
But this stopped when I found no solution for memcheck.

I still believe a multi-threaded valgrind is relevant for some tools such as callgrind
that do not depend (too much) on a "central data structure accessed on a permanent basis".

And maybe new things/instructions such as rseq might maybe provide a solution for memcheck
(avoiding the performance killer to protect the memcheck V bits infrastructure for any
access done by the guest).

But I agree with you that it is unlikely to appear very soon. On my side, I am not
expecting to have time to work on that prototype before I am retired
(but this time gets closer every day :).

> 
> What I'm thinking of is 2025.04, 2025.10 etc.
> 
> Thoughts?

On this aspect, I do not have strong preference but the "year" based approach makes
more clear when someone complains that they are using a (very) old release.

> 
> A+
> 
> Paul
> 
> 
> 
> 
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers