|
From: Julian S. <js...@ac...> - 2020-02-05 08:40:13
|
Greetings. In the Developer Toolroom at FOSDEM20 last Sunday, there was a bit of discussion regarding the release date for 3.16.0. The following was agreed: * freeze for large changes on Monday 2 March 2020. * final release on Monday 16 March 2020. This gives us just under four weeks to land any large changes for 3.16, followed by a two week stabilisation period before the release. My list of changes still to do for 3.16 are: * make the new &&-idiom-recognition stuff work also on s390 and MIPS. This was discussed with both the s390 and MIPS folks on Sunday. If it is not fixable in the timescale, it's not a disaster since that functionality can remain disabled on those targets, as it is now. But if possible it would be nice to have it fixed. * 64-bit time-related syscalls on 32-bit Linux targets are now failing (esp for Fedora Rawhide). Mark and/or me can look at this; other volunteers welcome. * Continue testing with gcc 10 (and maybe glibc-the-latest?); make sure it works. * [me] I'd like to land 253657 (improvements to PDB reading) if possible. * I would like to remove the exp-sgcheck tool. It hasn't been usable for years (if ever); it doesn't work at all on non-x86/amd64 targets, and is generally pointless to keep around. Are there any objections to removing it? * I'll make another pass through the open bugs within the next week, but I'm not aware of any critical bugs right now. If this schedule is a problem for anyone, please let us know immediately. Also, of course, if there are other changes that should go in 3.16, speak up now. J |
|
From: Julian S. <js...@ac...> - 2020-02-05 09:03:02
|
On 05/02/2020 09:49, Olaf Hering wrote: > On Wed, Feb 05, Julian Seward wrote: > Would you consider fixing Xen for this release? Yes. IIUC, you're referring to https://bugs.kde.org/show_bug.cgi?id=390553#c6. Yes? Please attach a patch (not a PR) to bug 390553 which changes the current sources in a way which you think is suitable. I have neither the expertise nor time to get into the details of Xen ioctls/syscalls, but I am happy to review and land patch(es) for Xen support. J |
|
From: Olaf H. <ol...@ae...> - 2020-02-05 09:07:42
|
On Wed, Feb 05, Julian Seward wrote: > Also, of course, if there are other changes that should go in 3.16, speak up now. Would you consider fixing Xen for this release? The recent commit just stuffed some constants into the switch statements, which does not "add support for Xen x.y". If not, I will just rest my case. Olaf |
|
From: Olaf H. <ol...@ae...> - 2020-02-05 09:11:46
|
Am Wed, 5 Feb 2020 10:02:49 +0100 schrieb Julian Seward <js...@ac...>: > Please attach a patch (not a PR) to bug 390553 which changes the current > sources in a way which you think is suitable. I will do so until this Friday. Olaf |
|
From: Philippe W. <phi...@sk...> - 2020-02-06 07:09:10
|
On Wed, 2020-02-05 at 09:40 +0100, Julian Seward wrote: > Also, of course, if there are other changes that should go in 3.16, speak up > now. I am wondering what we should do for prwritev (and similar syscall) supp entries not working anymore: https://bugs.kde.org/show_bug.cgi?id=417075 The origin of this bug has been identified as a backward incompatible change introduced in 3.15: some suppression entries working with 3.14 and before will not suppress anymore the same error in 3.15, but fixing this backward incompatibility in 3.16 might mean we are then breaking the supp entries working with 3.15 :(. Philippe |
|
From: Olaf H. <ol...@ae...> - 2020-02-07 19:53:21
|
Am Wed, 5 Feb 2020 10:11:26 +0100 schrieb Olaf Hering <ol...@ae...>: > I will do so until this Friday. While I do have something that actually works with xen 4.13, it is not yet ready to submit. Olaf |
|
From: Olaf H. <ol...@ae...> - 2020-02-28 15:27:30
|
Am Fri, 7 Feb 2020 20:52:57 +0100 schrieb Olaf Hering <ol...@ae...>: > Am Wed, 5 Feb 2020 10:11:26 +0100 > schrieb Olaf Hering <ol...@ae...>: > > I will do so until this Friday. > While I do have something that actually works with xen 4.13, it is not yet ready to submit. Doing a rebase of my batch of fixes onto the broken commit from bug#407376 was REALLY time consuming. Please consult both submitters next time when conflicting changes are proposed for inclusion. It would have been much easier for everyone involved to get the individual changes in git. I have updated bug#390553. This will not be the last batch of required changes, but this is all I can offer for the planned release. Olaf |
|
From: Mark W. <ma...@kl...> - 2020-02-09 11:02:20
|
Hi Julian, On Wed, Feb 05, 2020 at 09:40:03AM +0100, Julian Seward wrote: > In the Developer Toolroom at FOSDEM20 last Sunday, there was a bit of > discussion regarding the release date for 3.16.0. The following was agreed: > > * freeze for large changes on Monday 2 March 2020. > > * final release on Monday 16 March 2020. > > This gives us just under four weeks to land any large changes for 3.16, > followed by a two week stabilisation period before the release. This would be nice for the Fedora 32 schedule. 2020-03-17 is the current beta target (1 day after the 3.16.0 release). > My list of changes still to do for 3.16 are: > > * make the new &&-idiom-recognition stuff work also on s390 and MIPS. This > was discussed with both the s390 and MIPS folks on Sunday. If it is not > fixable in the timescale, it's not a disaster since that functionality can > remain disabled on those targets, as it is now. But if possible it would be > nice to have it fixed. > > * 64-bit time-related syscalls on 32-bit Linux targets are now failing (esp > for Fedora Rawhide). Mark and/or me can look at this; other volunteers > welcome. This is https://bugs.kde.org/show_bug.cgi?id=416753 It is 20 new time64 syscall variants. The syscall numbers are the same on all arches. > * Continue testing with gcc 10 (and maybe glibc-the-latest?); make sure it > works. I have been building valgrind 3.15.0 with backports against Fedora rawhide, which contains both gcc10 pre-release and glibc 3.21. Things now look reasonable on most architectures Fedora supports except for x86 and armhf because they are 32bit arches where the new glibc defaults to the new time syscalls. See valgrind f32 build.logs from: https://koji.fedoraproject.org/koji/packageinfo?packageID=98 They contain make regtest results plus .diff files. > * [me] I'd like to land 253657 (improvements to PDB reading) if possible. > > * I would like to remove the exp-sgcheck tool. It hasn't been usable for > years (if ever); it doesn't work at all on non-x86/amd64 targets, and is > generally pointless to keep around. Are there any objections to removing > it? Yes, please! > * I'll make another pass through the open bugs within the next week, but I'm > not aware of any critical bugs right now. https://bugs.kde.org/show_bug.cgi?id=417075 pwritev(vector[...]) suppression ignored Is somewhat annoying, but I am not sure how to proceed. https://bugs.kde.org/show_bug.cgi?id=416760 ppc64le Assertion 'VG_IS_16_ALIGNED(sizeof(struct rt_sigframe))' failed Is a regression caused by the fix for https://bugs.kde.org/show_bug.cgi?id=405201 Incorrect size of struct vki_siginfo on 64-bit Linux architectures > If this schedule is a problem for anyone, please let us know immediately. > Also, of course, if there are other changes that should go in 3.16, speak up > now. Looks doable to me. Thanks, Mark |
|
From: Nicholas N. <n.n...@gm...> - 2020-02-14 19:34:46
|
Hi, I have a plan to flip a couple of option defaults for cg_annotate and callgrind_annotate. - Change `--auto=no` to `--auto=yes`. This controls whether source code annotation occurs automatically. It was first implemented way back in 2001 or 2002 and I don't think I have ever run either tool without using `--auto=yes`. - Change `--show-percs=no` to `--show-percs=yes`. I added this option in 3.15 and have never not used it since. It makes the output much nicer to read. In short, I don't like programs with `--make-it-actually-work` options, and I consider both of these to be such options. Let me know if you object, otherwise I will land the changes at the end of the coming week. I will mention them in the NEWS file. Nick On Wed, 5 Feb 2020 at 19:40, Julian Seward <js...@ac...> wrote: > Greetings. > > In the Developer Toolroom at FOSDEM20 last Sunday, there was a bit of > discussion regarding the release date for 3.16.0. The following was > agreed: > > * freeze for large changes on Monday 2 March 2020. > > * final release on Monday 16 March 2020. > > This gives us just under four weeks to land any large changes for 3.16, > followed by a two week stabilisation period before the release. > > My list of changes still to do for 3.16 are: > > * make the new &&-idiom-recognition stuff work also on s390 and MIPS. This > was discussed with both the s390 and MIPS folks on Sunday. If it is not > fixable in the timescale, it's not a disaster since that functionality > can > remain disabled on those targets, as it is now. But if possible it > would be > nice to have it fixed. > > * 64-bit time-related syscalls on 32-bit Linux targets are now failing (esp > for Fedora Rawhide). Mark and/or me can look at this; other volunteers > welcome. > > * Continue testing with gcc 10 (and maybe glibc-the-latest?); make sure it > works. > > * [me] I'd like to land 253657 (improvements to PDB reading) if possible. > > * I would like to remove the exp-sgcheck tool. It hasn't been usable for > years (if ever); it doesn't work at all on non-x86/amd64 targets, and is > generally pointless to keep around. Are there any objections to > removing > it? > > * I'll make another pass through the open bugs within the next week, but > I'm > not aware of any critical bugs right now. > > If this schedule is a problem for anyone, please let us know immediately. > Also, of course, if there are other changes that should go in 3.16, speak > up > now. > > J > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |