[OMPT] Align implementation of reenter frame address to latest (frozen) version of...
authorJonas Hahnfeld <Hahnfeld@itc.rwth-aachen.de>
Wed, 14 Sep 2016 13:59:13 +0000 (13:59 +0000)
committerJonas Hahnfeld <Hahnfeld@itc.rwth-aachen.de>
Wed, 14 Sep 2016 13:59:13 +0000 (13:59 +0000)
commitfd0614d8308634755dbf77a0c448a235e97b78b3
treec1a67b3328f71dd7db90d0e649da31e47f8eeddc
parent464cdca9d35c0196a87a1e1971c313554ff41a3b
[OMPT] Align implementation of reenter frame address to latest (frozen) version of OMPT spec

The latest OMPT spec changed the semantic of a tasks reenter frame to be the application frame, that will be entered, when the runtime frame drops.
Before it was the last frame in the runtime. This doesn't work for some gcc execution pathes or even clang generated code for :
Since there is no runtime frame between the executed task and the encountering task.

The test case compares exit and reenter addresses against addresses captured in application code

Patch by Joachim Protze!

Differential Revision: https://reviews.llvm.org/D23305

llvm-svn: 281464
openmp/runtime/src/kmp_csupport.c
openmp/runtime/src/kmp_gsupport.c
openmp/runtime/src/kmp_runtime.c
openmp/runtime/src/kmp_tasking.c
openmp/runtime/src/ompt-specific.c
openmp/runtime/test/ompt/parallel/nested.c