Joachim Protze fdc9dfc8e4 [OpenMP][Tool] Add Archer option to disable data race analysis for sequential part ... This introduces the new `ARCHER_OPTIONS` flag `ignore_serial=0|1` to disable analysis and logging of memory accesses in the sequential part of the OpenMP application. In the sequential part of an OpenMP program no data race is possible, unless there is non-OpenMP concurrency (such as pthreads, MPI, ...). For the latter reason, this is not active by default. Besides reducing the runtime overhead for the sequential part of the program, this reduces the memory overhead for sequential initialization. In combination with `flush_shadow=1` this can allow analysis of applications, which run close to the limit of available memory, but only access smaller parts of shared memory during each OpenMP parallel region. A problem for this approach is that Archer only gets active, when the OpenMP runtime gets initialized, which might be after serial initialization of the application. In such case, it helps to call for example `omp_get_max_threads()` at the beginning of main. Differential Revision: https://reviews.llvm.org/D90473		2020-11-16 10:45:21 +01:00
..
analyzer	[OpenMP] Begin Adding OpenMP Tool to Gather OpenMP Information	2020-11-11 20:00:37 -05:00
archer	[OpenMP][Tool] Add Archer option to disable data race analysis for sequential part	2020-11-16 10:45:21 +01:00
multiplex	[OpenMP][Tools][Tests] Fix ompt multiplex test	2020-11-12 01:43:49 +01:00
CMakeLists.txt