f8bdacbadc
Value, type, and instantiation dependence were not being handled correctly for CUDAKernelCallExpr AST nodes. As a result, if an undeclared identifier was used in the triple-angle-bracket kernel call configuration, there would be no error during parsing, and there would be a crash during code gen. This patch makes sure that an error will be issued during parsing in this case, just as there would be for any other use of an undeclared identifier in C++. Patch by Jason Henline. Reviewers: jlebar, rsmith Differential Revision: http://reviews.llvm.org/D15858 llvm-svn: 257839
29 lines
827 B
Plaintext
29 lines
827 B
Plaintext
// RUN: %clang_cc1 -fsyntax-only -verify %s
|
|
|
|
#include "Inputs/cuda.h"
|
|
|
|
__global__ void g1(int x) {}
|
|
|
|
template <typename T> void t1(T arg) {
|
|
g1<<<arg, arg>>>(1);
|
|
}
|
|
|
|
void h1(int x) {}
|
|
int h2(int x) { return 1; }
|
|
|
|
int main(void) {
|
|
g1<<<1, 1>>>(42);
|
|
g1(42); // expected-error {{call to global function g1 not configured}}
|
|
g1<<<1>>>(42); // expected-error {{too few execution configuration arguments to kernel function call}}
|
|
g1<<<1, 1, 0, 0, 0>>>(42); // expected-error {{too many execution configuration arguments to kernel function call}}
|
|
|
|
t1(1);
|
|
|
|
h1<<<1, 1>>>(42); // expected-error {{kernel call to non-global function h1}}
|
|
|
|
int (*fp)(int) = h2;
|
|
fp<<<1, 1>>>(42); // expected-error {{must have void return type}}
|
|
|
|
g1<<<undeclared, 1>>>(42); // expected-error {{use of undeclared identifier 'undeclared'}}
|
|
}
|