Re: [Valgrind-developers] Next version numbering

[LATHUILIERE B. <bru...@ed...>]

Hi,

I think the tool verrou could be able to benefit from a multi-threaded version (at least for a subset of functionalities).
I've well understood, a multi-threaded version is not for a near future. Nevertheless, do you have any advice for tool developers to be ready this revolution?   Typically, I'd like to know if it will be possible to use TLS?

It sounds ridiculous "to do nothing faster", but for tools like callgrind or verrou which can select a part of the code to be instrumented it could be useful.

++
Bruno


-----Message d'origine-----
De : val...@li... <val...@li...>
Envoyé : jeudi 1 mai 2025 09:58
À : Paul Floyd <pj...@wa...>; val...@li...
Objet : Re: [Valgrind-developers] Next version numbering

Expéditeur externe : Vérifier l'expéditeur avant de cliquer sur les liens ou pièces-jointes

External Sender : Check the sender before clicking any links or attachments

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://list/
> s.sourceforge.net%2Flists%2Flistinfo%2Fvalgrind-developers&data=05%7C0
> 2%7Cbruno.lathuiliere%40edf.fr%7Cb1235c6617ec44ac5b9f08dd88883a49%7Ce2
> 42425b70fc44dc9ddfc21e304e6c80%7C1%7C0%7C638816840845605483%7CUnknown%
> 7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z
> MiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=B%2ByBnnYvvJ60
> %2F9zAq1%2F56V21COCltsHFR5lW2rIXScA%3D&reserved=0



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

Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________

This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or virus-free.