[Openmp-commits] [PATCH] D13689: Add OMPT events for API locking

[John Mellor-Crummey via Openmp-commits]

I am fine with the approach proposed below. We can refine the interface at a later date when the lock hints become available.
--
John Mellor-Crummey         Professor
Dept of Computer Science    Rice University
email: johnmc at rice.edu      phone: 713-348-5179

> On Oct 13, 2015, at 11:46 AM, Tim Cramer <cramer at itc.rwth-aachen.de> wrote:
> 
> tcramer added a comment.
> 
> In http://reviews.llvm.org/D13689#265984, @jmellorcrummey wrote:
> 
>> In reading this patch over again, I realized that you implemented the OMPT TR2 lock initialization callback rather than the OMPT working draft, which also passes a lock hint and a lock type to the init callback. The OMPT implementation in LLVM OpenMP is evolving with the current version of the OMPT draft. There are features already in the code that aren't in OMPT TR2. Fort that reason, I think you should add the lock hint and lock type parameters.
> 
> 
> Thats true. However, the OpenMP runtime library routine "omp_init_lock_with_hint" seems not to be implemented at the moment, because it will come with OpenMP 4.5 (aka 4.1). Thus, I can only pass a hard-coded 0 (which will be omp_lock_hint_none) as hint at the moment.
> 
> I agree that the lock type is already implementable, but since it is a change in OMPT infrastructure itself, it should be a separated patch anyway.
> 
> I would propose to use the old signature for now and change it as soon as we have the new locking library routine. Does that sound reasonable?
> 
> 
> Repository:
>  rL LLVM
> 
> http://reviews.llvm.org/D13689
> 
> 
> 
> 
> !DSPAM:8504,561d356a315681832012833!
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/openmp-commits/attachments/20151013/7db8e44c/attachment.html>