|
From: <pa...@fr...> - 2016-12-09 19:26:24
|
Hi After lurking here for a few years, I think it's time that I contributed something a bit more concrete. At the moment I have two ideas: Add C++17 support. I also lurk on the BSI C++ panel. Obviously C++17 is not done yet. The first changes that I see are the additional alignment overloads for operator new, see if polymorphic_allocator needs any support. I haven't been through the changes to threads but I imagine there may be things there as well. Do you think that this is too experimental/bleeding edge for Valgrind? Update FreeBSD support. Currently FreeBSD has a version of Valgrind 10.1 available. Initially I'd just like to get it to build and function. After that I'm sure that there are lots of other things like missing syscalls. I've started looking at merging the existing code (the bitbucket FreeBSD repo and Valgrind head), and it looks like a fairly major task, if nothing else there are many manual merges where Solaris and TileGX have been added. Also early next year I'm planning to retire my venerable Macbook (too old to upgrade beyond Mac OS 10.7.5) and get either another Macbook or a Mac Mini. So that might lead to some work on macOS. One caveat: though this would be on my own time, my employer does, in a different business unit, sell software integrity tools, so I'll need to check that there's no problem there. Regards Paul |
|
From: Rhys K. <rhy...@gm...> - 2016-12-11 00:47:22
|
On 9 December 2016 at 14:26, <pa...@fr...> wrote: > Hi > > After lurking here for a few years, I think it's time that I contributed > something a bit more concrete. > > At the moment I have two ideas: > > Add C++17 support. > I also lurk on the BSI C++ panel. Obviously C++17 is not done yet. The > first changes that I see are the additional alignment overloads for > operator new, see if polymorphic_allocator needs any support. I haven't > been through the changes to threads but I imagine there may be things there > as well. Do you think that this is too experimental/bleeding edge for > Valgrind? > > Update FreeBSD support. > Currently FreeBSD has a version of Valgrind 10.1 available. Initially I'd > just like to get it to build and function. After that I'm sure that there > are lots of other things like missing syscalls. I've started looking at > merging the existing code (the bitbucket FreeBSD repo and Valgrind head), > and it looks like a fairly major task, if nothing else there are many > manual merges where Solaris and TileGX have been added. > > Also early next year I'm planning to retire my venerable Macbook (too old > to upgrade beyond Mac OS 10.7.5) and get either another Macbook or a Mac > Mini. So that might lead to some work on macOS. > Another macOS developer for Valgrind would be welcome. > > One caveat: though this would be on my own time, my employer does, in a > different business unit, sell software integrity tools, so I'll need to > check that there's no problem there. > > Regards > Paul > ------------------------------------------------------------ > ------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/xeonphi > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Philippe W. <phi...@sk...> - 2016-12-11 22:11:38
|
On Fri, 2016-12-09 at 20:26 +0100, pa...@fr... wrote: > Hi > > After lurking here for a few years, I think it's time that I > contributed something a bit more concrete. > > At the moment I have two ideas: > > Add C++17 support. I also lurk on the BSI C++ panel. Obviously C++17 is > not done yet. The first changes that I see are the additional alignment > overloads for operator new, see if polymorphic_allocator needs any > support. I haven't been through the changes to threads but I imagine > there may be things there as well. Do you think that this is too > experimental/bleeding edge for Valgrind? No idea if C++17 is to be considered experimental or not. However, note that there are still some work to do for previous versions of C++. See bugs Bug 373069 - memcheck/tests/leak_cpp_interior fails with GCC 5.1+ Bug 372347 - Replacement problem of the additional c++14/c++17 new and delete operators > > Update FreeBSD support. Currently FreeBSD has a version of Valgrind > 10.1 available. Initially I'd just like to get it to build and > function. After that I'm sure that there are lots of other things like > missing syscalls. I've started looking at merging the existing code > (the bitbucket FreeBSD repo and Valgrind head), and it looks like a > fairly major task, if nothing else there are many manual merges where > Solaris and TileGX have been added. Yes, this is not a minor task. You might discuss this at the FOSDEM 17 Valgrind devroom and see if there is (some) enthusiasm for merging FreeBSD upstream. Philippe |
|
From: Paul F. <pa...@fr...> - 2016-12-16 06:56:59
|
On 11 Dec 2016, at 23:13, Philippe Waroquiers wrote: > On Fri, 2016-12-09 at 20:26 +0100, pa...@fr... wrote: >> Hi >> >> After lurking here for a few years, I think it's time that I >> contributed something a bit more concrete. >> >> At the moment I have two ideas: >> >> Add C++17 support. I also lurk on the BSI C++ panel. Obviously C++17 is >> not done yet. The first changes that I see are the additional alignment >> overloads for operator new, see if polymorphic_allocator needs any >> support. I haven't been through the changes to threads but I imagine >> there may be things there as well. Do you think that this is too >> experimental/bleeding edge for Valgrind? > No idea if C++17 is to be considered experimental or not. > However, note that there are still some work to do for previous versions > of C++. See bugs > Bug 373069 - memcheck/tests/leak_cpp_interior fails with GCC 5.1+ > Bug 372347 - Replacement problem of the additional c++14/c++17 new and > delete operators > I had a look at the bugzilla items, and 372347 is pretty much what I was referring to. I need to look at the second one a bit more. By experimental I mean that, for instance, clang support is only at subversion head, not yet in an official release. >> >> Update FreeBSD support. Currently FreeBSD has a version of Valgrind >> 10.1 available. Initially I'd just like to get it to build and >> function. After that I'm sure that there are lots of other things like >> missing syscalls. I've started looking at merging the existing code >> (the bitbucket FreeBSD repo and Valgrind head), and it looks like a >> fairly major task, if nothing else there are many manual merges where >> Solaris and TileGX have been added. > Yes, this is not a minor task. > You might discuss this at the FOSDEM 17 Valgrind devroom and see > if there is (some) enthusiasm for merging FreeBSD upstream. > OK, I'll leave FreeBSD for now. I'm not likely to go to FOSDEM, though I might try to catch some videos if possible. A+ Paul |