[all-commits] [llvm/llvm-project] b1b441: [Attributor] Use abstract call sites to determine ...

[Johannes Doerfert via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: b1b441d22de88ec9816403ab6d0541ca91faba16
      https://github.com/llvm/llvm-project/commit/b1b441d22de88ec9816403ab6d0541ca91faba16
  Author: Johannes Doerfert <johannes at jdoerfert.de>
  Date:   2019-12-31 (Tue, 31 Dec 2019)

  Changed paths:
    M llvm/include/llvm/IR/CallSite.h
    M llvm/include/llvm/Transforms/IPO/Attributor.h
    M llvm/lib/IR/AbstractCallSite.cpp
    M llvm/lib/Transforms/IPO/Attributor.cpp
    M llvm/test/Transforms/Attributor/IPConstantProp/PR26044.ll
    M llvm/test/Transforms/Attributor/IPConstantProp/openmp_parallel_for.ll
    M llvm/test/Transforms/Attributor/IPConstantProp/pthreads.ll
    M llvm/test/Transforms/Attributor/IPConstantProp/thread_local_acs.ll
    M llvm/test/Transforms/Attributor/callbacks.ll

  Log Message:
  -----------
  [Attributor] Use abstract call sites to determine associated arguments

This is the second step after D67871 to make use of abstract call sites.
In this patch the argument we associate with a abstract call site
argument can be the one in the callback callee instead of the one in the
callback broker.

Caveat: We cannot allow no-alias arguments for problematic callbacks:
As described in [1], adding no-alias (or restrict) to arguments could
break synchronization as the synchronization effect, e.g., a barrier,
does not "alias" with the pointer anymore. This disables no-alias
annotation for potentially problematic arguments until we implement the
fix described in [1].

Reviewed By: uenoku

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

[1] Compiler Optimizations for OpenMP, J. Doerfert and H. Finkel,
    International Workshop on OpenMP 2018,
    http://compilers.cs.uni-saarland.de/people/doerfert/par_opt18.pdf