Re: [Valgrind-developers] valgrind 3.17.0 release plan?

[Carl L. <ce...@us...>]

Mark, Julian:

For PPC64, we have the remaining ISA 3.1 instruction support that we
would like to get in for the 3.17 release.  There are two existing
bugzillas for the support.

https://bugs.kde.org/show_bug.cgi?id=429354
https://bugs.kde.org/show_bug.cgi?id=429375

The patches in these two bugzillas have been reviewed once by Julian. 
I have updated the patches in both bugzillas per Julian's comments.  I
am hopefull the patches will be approved when Julian can review them
again. 

The final set of patches for the ISA 3.1 support were posted today in
bugzilla:

https://bugs.kde.org/show_bug.cgi?id=433801

These patches are fairly straight forward.  I hope we can get them
approved fairly quickly so they can be included in the 3.17.0 release.

We have an outstanding issue with the scv instruction support, as you
know.  

https://bugs.kde.org/show_bug.cgi?id=431157

Looking at your email and internal discussions, it looks like we need
the Linux kernel 5.10.14 and the latest glibc to properly test the
patch I created.  My testing todate has been on an older kernel using a
compiler that I have am now told does not have the scv support.  I
think this issue will need a lot more time before it is ready to be
included in mainline.  This fix should not be included in 3.17.0.

Additionally, we have noticed a number of helgrind failures in our
testing on the latest internal prototype hardware with the latest
internal compiler.  We are investigating these issues.  Currently, they
do not appear to be related to the ISA 3.1 support.  We will update you
on these issues as we dig into them further.

Thanks.

                      Carl Love

On Mon, 2021-03-01 at 14:39 +0100, Mark Wielaard wrote:
> Hi,
> 
> We discussed doing a valgrind 3.17.0 release on irc a couple of
> times,
> but don't really seem to have a concrete plan. My hope was that we
> could get everything in before March 1st and then do an RC.
> 
> But it is March 1 today and I think we aren't really ready yet.
> 
> So can we make a more concrete plan for 3.17.0?
> 
> What are the things people believe should go in and which things are
> just nice to have? What would be a good cut-off date when we can
> create
> a release branch/candidate and only fix release blockers/regressions?
> 
> I tried to go through all the bugs being reported (or changed) since
> 3.16.1 was released. And I would like to fix the following:
> 
>   - 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.redhat.com_show-5Fbug.cgi-3Fid-3D1923493&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=RFEmMkZAk--_wFGN5tkM_A&m=htkczODBVgZIXIqrdosIQgJ_rxmXquoMOwpUVQlMc2I&s=D6hL4wfEjz7IOy7eu9P2oeeST2QaXmendCcJCFXs0AE&e=
>  
>     netresolve: FTBFS in Fedora rawhide/f34 because valgrind breaks
>     on arm64
> 
>   - 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_show-5Fbug.cgi-3Fid-3D396656&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=RFEmMkZAk--_wFGN5tkM_A&m=htkczODBVgZIXIqrdosIQgJ_rxmXquoMOwpUVQlMc2I&s=BIvrGz7rL1Yklgqvmt9rYswaJ6E7g8IVGgBx8yxVOhE&e=
>  
>     
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_show-5Fbug.cgi-3Fid-3D427969&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=RFEmMkZAk--_wFGN5tkM_A&m=htkczODBVgZIXIqrdosIQgJ_rxmXquoMOwpUVQlMc2I&s=RfDoGaOrXtWGB7V9Vl5Sfig4-7luXGG09uyz5kZWmdM&e=
>  
>     Debian/Ubuntu use dwz in an odd way it seems.
> 
>   - 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_show-5Fbug.cgi-3Fid-3D432870&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=RFEmMkZAk--_wFGN5tkM_A&m=htkczODBVgZIXIqrdosIQgJ_rxmXquoMOwpUVQlMc2I&s=mWKhcMBN7HPGbr1gZXV40laMFZDqlJty34zy87JvpVw&e=
>  
>     gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64
> 
>   - 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_show-5Fbug.cgi-3Fid-3D431306&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=RFEmMkZAk--_wFGN5tkM_A&m=htkczODBVgZIXIqrdosIQgJ_rxmXquoMOwpUVQlMc2I&s=He956C62mh9RbIItPR82QcswHNEGP221hU0h-lYt-WU&e=
>  
>     Update demangler to support Rust v0 name mangling
> 
> Where the last one is just a nice to have.
> 
> I believe things can be ready for a 3.17.0 release branch/candidate
> by
> end of this week, Friday March 5.
> 
> If people have other bugs they like to really get resolved for 3.17.0
> please let me know and I can see how I can help.
> 
> Cheers,
> 
> Mark
> 
> 
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_valgrind-2Ddevelopers&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=RFEmMkZAk--_wFGN5tkM_A&m=htkczODBVgZIXIqrdosIQgJ_rxmXquoMOwpUVQlMc2I&s=0qiyjFjH3fr9ITog5R-mqlMMSYId9Q45YVQC8J0DKI0&e=