On Wed, Jan 02, 2019 at 06:23:57PM +0100, Ulrich Drepper wrote:
> On 1/2/19 6:21 PM, Jakub Jelinek wrote:
> > As we aren't implementing OpenMP 5.0 fully yet and especially because
> > we aren't implementing the new nesting ICV semantics, we shouldn't do it 
> > now,
> > they are valid in OpenMP 4.5.
> 
> OK, that applies to omp_[gs]et_nested.
> 
> How about the lock symbols?  All the sync symbols are already defined as
> aliases (or more correctly, the other way around).  The sooner people
> change, the better, and at least those parts of OpenMP5 are "implemented".

We ignore the hints, so "implemented" is the right term ;).

I'd say there is no hurry for them either, I believe what is deprecated in
5.0 is going to be removed only (if at all) in 6.0, so like 5 years from
now, so waiting until we implement all of OpenMP 5.0 shouldn't hurt that
much.

        Jakub

Reply via email to