Re: [Valgrind-developers] Project ideas

[Philippe W. <phi...@sk...>]

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