Use fuzzy return addresses in lock testcases so that these testcases can also be run using the Intel Compiler.
Diff was initially submitted in D41182.
Paths
| Differential D41896
[OMPT] Use fuzzy return addresses in lock testcases ClosedPublic Authored by sconvent on Jan 10 2018, 3:32 AM.
Details Summary Use fuzzy return addresses in lock testcases so that these testcases can also be run using the Intel Compiler. Diff was initially submitted in D41182.
Diff Detail Event TimelineComment Actions Still surprised that this is necessary for void function calls, but with that change the tests also succeed for intel compiler. This revision is now accepted and ready to land.Jan 17 2018, 1:15 AM Comment Actions I finally looked at an objdump and the Intel Compiler tries to use __kmpc_init_lock if available. This function has the advantage of taking the global thread id, so avoiding the cost of finding it in TLS. This patch fixes the problem, I'm going to submit it right away. Closed by commit rL323529: [OMPT] Use fuzzy return addresses in lock testcases (authored by Hahnfeld). · Explain WhyJan 26 2018, 6:21 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 129229 runtime/test/ompt/synchronization/lock.c
runtime/test/ompt/synchronization/nest_lock.c
runtime/test/ompt/synchronization/test_lock.c
runtime/test/ompt/synchronization/test_nest_lock_parallel.c
|