|
From: Mark W. <ma...@kl...> - 2023-02-03 10:53:00
|
Hi valgrind developers, Paul suggested that we should have a developer video chat again to discuss development issues. And I agree that would be a good thing to set some goals for the next release in April. We would like to meet on Friday February 10 at 16:00 UTC (17:00 CET, 11:00 EST). https://meet.jit.si/ValgrindDevMeeting Some issues we can discuss: - Pick a date for the April 3.21.0 release Critical bugs that are must fix? - Upstreaming risc-v - https://github.com/petrpavlu/valgrind-riscv64 - AVX512 status - https://bugs.kde.org/show_bug.cgi?id=383010 - loongarch - https://bugs.kde.org/show_bug.cgi?id=457504 - The macOS port status - do we have any users/developers? - https://bugs.kde.org/show_bug.cgi?id=433859 aligned and sized stuff. Do we have enough bits to track this efficiently? - Plugging into the new FORTIFY_SOURCE=3 support in glibc. valgrind memcheck should be able to show useful information about the memory block that triggered the fault. - Infrastructure stuff. We are still using the sourcefore mailinglist and the kde bugzilla. But our git repo and website are at sourceware. Should we migrate everything to sourceware? - Would that be a good point to switch from "master" to "main" for the main git branch name? We already largely avoid terms like black/whitelist and master/slave in the code and it would be a good transition towards more inclusive language as described in https://inclusivenaming.org/ These are all just suggestions. Please feel free to join and/or propose other topics, features or bugs to discuss. Cheers, Mark |