forked from OSchip/llvm-project
18e2d82297
Summary: Some function calls in CUDA are allowed to appear in semantically-correct programs but are an error if they're ever codegen'ed. Specifically, a host+device function may call a host function, but it's an error if such a function is ever codegen'ed in device mode (and vice versa). Previously, clang made no attempt to catch these errors. For the most part, they would be caught by ptxas, and reported as "call to unknown function 'foo'". Now we catch these errors and report them the same as we report other illegal calls (e.g. a call from a host function to a device function). This has a small change in error-message behavior for calls that were previously disallowed (e.g. calls from a host to a device function). Previously, we'd catch disallowed calls fairly early, before doing additional semantic checking e.g. of the call's arguments. Now we catch these illegal calls at the very end of our semantic checks, so we'll only emit a "illegal CUDA call" error if the call is otherwise well-formed. Reviewers: tra, rnk Subscribers: cfe-commits Differential Revision: https://reviews.llvm.org/D23242 llvm-svn: 278759 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| address-spaces.cu | ||
| alias.cu | ||
| convergent.cu | ||
| cuda-builtin-vars.cu | ||
| device-stub.cu | ||
| device-var-init.cu | ||
| device-vtable.cu | ||
| filter-decl.cu | ||
| flush-denormals.cu | ||
| fp-contract.cu | ||
| function-overload.cu | ||
| kernel-args-alignment.cu | ||
| kernel-call.cu | ||
| launch-bounds.cu | ||
| link-device-bitcode.cu | ||
| llvm-used.cu | ||
| printf-aggregate.cu | ||
| printf.cu | ||
| ptx-kernels.cu | ||