Re: [Valgrind-developers] Project ideas

[Rhys K. <rhy...@gm...>]

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
>