llvm-project/llvm/test/Transforms/RewriteStatepointsForGC
Daniel Neilson 2574d7cbf6 All libcalls should be considered to be GC-leaf functions.
Summary:
It is possible for some passes to materialize a call to a libcall (ex: ldexp, exp2, etc),
but these passes will not mark the call as a gc-leaf-function. All libcalls are
actually gc-leaf-functions, so we change llvm::callsGCLeafFunction() to tell us that
available libcalls are equivalent to gc-leaf-function calls.

Reviewers: sanjoy, anna, reames

Reviewed By: anna

Subscribers: llvm-commits

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

llvm-svn: 309291
2017-07-27 16:49:39 +00:00
..
base-pointers-1.ll
base-pointers-2.ll
base-pointers-3.ll
base-pointers-4.ll
base-pointers-5.ll
base-pointers-6.ll
base-pointers-7.ll
base-pointers-8.ll
base-pointers-9.ll
base-pointers-10.ll
base-pointers-11.ll
base-pointers-12.ll
base-pointers-13.ll
base-pointers.ll
base-vector.ll
basic.ll
basics.ll
call-gc-result.ll
codegen-cond.ll
constants.ll
deopt-intrinsic-cconv.ll
deopt-intrinsic.ll
deopt-lowering-attrs.ll
deref-pointers.ll
drop-invalid-metadata.ll
gc-relocate-creation.ll
invokes.ll
leaf-function.ll
libcall.ll All libcalls should be considered to be GC-leaf functions. 2017-07-27 16:49:39 +00:00
live-vector-nosplit.ll
liveness-basics.ll
patchable-statepoints.ll
preprocess.ll
relocate-invoke-result.ll
relocation.ll
rematerialize-derived-pointers.ll
rewrite-invoke.ll
statepoint-attrs.ll
statepoint-calling-conventions.ll
statepoint-coreclr.ll
statepoint-format.ll
two-invokes-one-landingpad.ll