forked from OSchip/llvm-project
9b9294674b
C++ emits vtables for classes that have key function present in the current TU. While we compile CUDA the fact that key function was found in this TU does not mean that we are going to generate code for it. E.g. vtable for a class with host-only methods should not (and can not) be generated on device side, because we'll never generate code for them during device-side compilation. This patch adds an extra CUDA-specific check during key method computation and filters out potential key methods that are not suitable for this side of CUDA compilation. When we codegen vtable, entries for unsuitable methods are set to null. Differential Revision: http://reviews.llvm.org/D15309 llvm-svn: 255911 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| address-spaces.cu | ||
| cuda-builtin-vars.cu | ||
| device-stub.cu | ||
| device-vtable.cu | ||
| filter-decl.cu | ||
| function-overload.cu | ||
| host-device-calls-host.cu | ||
| kernel-call.cu | ||
| launch-bounds.cu | ||
| link-device-bitcode.cu | ||
| llvm-used.cu | ||
| ptx-kernels.cu | ||