ABataev added a comment. In D94315#2487150 <https://reviews.llvm.org/D94315#2487150>, @JonChesterfield wrote:
> I'm guessing we're using the function boundary as a compiler barrier. That > seems fragile in the face of improving cross-function optimisation. Looks like applying inaccessiblemem_or_argmemonly attribute to the OpenMP functions is way too optimistic since we still can access this (inaccessible) memory using other OpenMP functions. Not sure about the semantics of this attribute, though. > What is the invariant we want around entry to a data environment, which > happens to be met by a function boundary? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D94315/new/ https://reviews.llvm.org/D94315 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
