On 10/9/2022 11:25 PM, Maris Nartiss wrote:
There is no issue with supporting both OpenMP and pthreads as most of libraries use neither of them. There are a few modules with some parallelism implemented and in such case they use only one of options thus bypassing any compatibility issues per se.
This is true today. Will it be true tomorrow? Some guidelines are in order.
As for valgrind noise – it comes from design decisions made decades a go – each module is a short running independent program and thus it is left to OS to reclaim memory at exit. Analysis tools sometimes also report potential uninitialized use but in cases that can not be reached during a normal GRASS module run. Unfortunately improving GRASS quite often is like restoring an ancient artefact where it is hard to tell bugs from features apart.
Valgrind's issue is it doesn't support OpenMP without tricking GCC into converting to pthreads, which completely defeats the point.
-- Best Regards, -Brad _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
