|
From: Julian S. <js...@ac...> - 2016-09-16 15:33:06
|
Hi All, I plan to branch for 3.12 next Monday. This is so as to make life easier for packagers and to provide a place to work out any stability/correctness issues before the release. The 3.12.0 release will be on Thursday 20 October, with a possible followup 3.12.1 release in mid December. I believe the trunk is in fairly good shape on Linux and Solaris. There are still quite a few bugs though that would be good to fix before the release, if possible. docs/internals/3_11_BUGSTATUS.txt summarises and tracks their status. I will track checkins to the trunk and merge to the branch as necessary. Please do let me know of any bugs you think should be fixed for 3.12, and of any checkins to merge. I am currently unsure about the status of the following ports: * MacOS X 10.12 * The linux-tilegx port. Is anyone maintaining this now? J |
|
From: Ivo R. <iv...@iv...> - 2016-09-16 16:09:48
|
2016-09-16 17:32 GMT+02:00 Julian Seward <js...@ac...>: > Please do let me know of any bugs you think should be fixed for 3.12, and of any checkins to merge. > Hi Julian, Patch for the following bug is ready to land, IMO. I'd like to have another set of eyeballs review the changes before I integrate it, though: 367995 Integration of memcheck with custom memory allocator Thanks, I. |
|
From: Julian S. <js...@ac...> - 2016-09-20 10:48:25
|
Ivo, Hi. > Patch for the following bug is ready to land, IMO. > I'd like to have another set of eyeballs review the changes before I > integrate it, though: > > 367995 Integration of memcheck with custom memory allocator Done -- comments in bugzilla. J |
|
From: Rhys K. <rhy...@gm...> - 2016-09-16 18:42:20
|
On Friday, September 16, 2016, Julian Seward <js...@ac...> wrote: > > Hi All, > > I plan to branch for 3.12 next Monday. This is so as to make life > easier for packagers and to provide a place to work out any > stability/correctness issues before the release. The 3.12.0 release > will be on Thursday 20 October, with a possible followup 3.12.1 > release in mid December. > > I believe the trunk is in fairly good shape on Linux and Solaris. > There are still quite a few bugs though that would be good to fix > before the release, if possible. docs/internals/3_11_BUGSTATUS.txt > summarises and tracks their status. I will track checkins to the > trunk and merge to the branch as necessary. Please do let me know of > any bugs you think should be fixed for 3.12, and of any checkins to > merge. > > I am currently unsure about the status of the following ports: > > * MacOS X 10.12 A patch set that provides the initial bring up on macOS 10.12 is on Bugzilla: https://bugs.kde.org/show_bug.cgi?id=365327 I hope to address the memory mapping problem over the weekend. > > * The linux-tilegx port. Is anyone maintaining this now? > > J > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > Valgrind-developers mailing list > Val...@li... <javascript:;> > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Julian S. <js...@ac...> - 2016-09-20 11:24:53
|
On 16/09/16 20:42, Rhys Kidd wrote: >> I am currently unsure about the status of the following ports: >> >> * MacOS X 10.12 > > A patch set that provides the initial bring up on macOS 10.12 is on > Bugzilla: > https://bugs.kde.org/show_bug.cgi?id=365327 Could you land that, sooner rather than later, so as to get any build system changes onto the branch sooner rather than later? It looks like those patches won't have any effect on the existing 10.11 support, correct? > I hope to address the memory mapping problem over the weekend. Thanks. J |
|
From: Rhys K. <rhy...@gm...> - 2016-09-22 02:58:21
|
On 20 September 2016 at 07:24, Julian Seward <js...@ac...> wrote: > On 16/09/16 20:42, Rhys Kidd wrote: > > >> I am currently unsure about the status of the following ports: > >> > >> * MacOS X 10.12 > > > > A patch set that provides the initial bring up on macOS 10.12 is on > > Bugzilla: > > https://bugs.kde.org/show_bug.cgi?id=365327 > > Could you land that, sooner rather than later, so as to get any build > system changes onto the branch sooner rather than later? It looks like > those patches won't have any effect on the existing 10.11 support, correct? > Landed in r15976, after confirming no regressions to 10.11 support. > I hope to address the memory mapping problem over the weekend. > > Thanks. > > J > > |
|
From: Matthias S. <zz...@ge...> - 2016-09-22 04:35:34
|
Hi Julian, Will the following issue also be considered for 3.12? 358697 - valgrind.h: Some code remains even when defining NVALGRIND It is about valgrind.h using volatile to silence a compiler warning. But it means that defining NVALGRIND will not make VALGRIND_PRINTF disappear completely from the binary. I vote for replacing volatile by something else. Regards Matthias |