On 10/14/2022 3:00 AM, Even Rouault wrote:
Hi,
just wanted to point that if you are interested in a "framework" for
submit jobs to a thread pool, I can point to
https://github.com/uclouvain/openjpeg/blob/master/src/lib/openjp2/thread.h
Hi,
just wanted to point that if you are interested in a "framework" for
submit jobs to a thread pool, I can point to
https://github.com/uclouvain/openjpeg/blob/master/src/lib/openjp2/thread.h
https://github.com/uclouvain/openjpeg/blob/master/src/lib/openjp2/thread.c
which is a port in C
Am 09.10.2022 20:45 schrieb Brad ReDacted:
Those variables would be...? Is this documented somewhere? If not, can
we get it documented?
https://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly
OpenMP can do far more than just loop "unrolling", these days. Tasking
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
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.
As for valgrind noise – it comes from design
Those variables would be...? Is this documented somewhere? If not, can
we get it documented?
OpenMP can do far more than just loop "unrolling", these days. Tasking
sections to run concurrent is also quite trivial. It can also offload to
GPU, etc. Check out the v4.5+ spec. It's pretty
Can still run GRASS outside the shell by setting all of the environment
variables appropriately ...
OpenMP just works by "unrolling" all of the determinate loops, i.e., the
ones that iterate a fixed number of times. No speedups to anything else.
Speedup from OpenMP will be limited,
Hello,
I'm working on adding parallelism to modules, but debugging is turning
out to be a logistical nightmare:
Why do I not get any reporting from GCC option '-fsanitize=address|thread"?
I am also having trouble getting the profiler to work properly inside
GRASS (I assume due to shell?).
