[Openmp-dev] [RFC] Clarify the absence of API stability for the *device runtime* (aka. libomptarget-nvptx-sm_XX.bc)

[Hal Finkel via Openmp-dev]

On 7/10/20 7:44 AM, Ye Luo via Openmp-dev wrote:
>
>     It seems that my experience that mixing an older version of libomp
>     and a newer version of libomptarget hangs the application
>     indicates the stability of libomp is limited at this point in time.
>
> Put a bit more words. I mean even for libomp which is thought to be 
> stable (API, semantics), it may cause problems and burn users.
> If mix-and-match is a critical feature in any part of 
> libomp/libomptarget, please make it solid by testing. If not, directly 
> stop users doing it.
> Ye


I fully agree. Our best intentions to keep the interface stable are 
insufficient to keep the interface stable without explicit testing. 
Testing is definitely required (or, alternatively, we should change the 
whole setup to make everything explicitly internalized).

  -Hal


>
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev

-- 
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20200710/69c2d225/attachment.html>