diff options
| author | Artem Belevich <tra@google.com> | 2015-12-17 18:12:36 +0000 |
|---|---|---|
| committer | Artem Belevich <tra@google.com> | 2015-12-17 18:12:36 +0000 |
| commit | 9b9294674b879d260b61b9176bc88a02d00265ac (patch) | |
| tree | a2cfad9265c4c029413047290540cb7a316add40 /lldb/packages/Python/lldbsuite/test/python_api/value/main.c | |
| parent | 8b524597efcef4ff37f667195516e468be66da6f (diff) | |
| download | bcm5719-llvm-9b9294674b879d260b61b9176bc88a02d00265ac.tar.gz bcm5719-llvm-9b9294674b879d260b61b9176bc88a02d00265ac.zip | |
[CUDA] Make vtable construction aware of host/device side of CUDA compilation.
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
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/main.c')
0 files changed, 0 insertions, 0 deletions
