a9d68a5524
In C++ and C2x, we would avoid calling ImplicitlyDefineFunction at all, but in OpenCL mode we would still call the function and have it produce an error diagnostic. Instead, we now have a helper function to determine when implicit function definitions are allowed and we use that to determine whether to call ImplicitlyDefineFunction so that the behavior is more consistent across language modes. This changes the diagnostic behavior from telling the users that an implicit function declaration is not allowed in OpenCL to reporting use of an unknown identifier and going through typo correction, as done in C++ and C2x.
23 lines
769 B
Common Lisp
23 lines
769 B
Common Lisp
// RUN: %clang_cc1 -verify %s -cl-std=CL1.2
|
|
// RUN: %clang_cc1 -verify %s -pedantic -DPEDANTIC -cl-std=CL1.2
|
|
// RUN: %clang_cc1 -verify %s -cl-std=CLC++
|
|
// RUN: %clang_cc1 -verify %s -pedantic -cl-std=CLC++
|
|
|
|
|
|
#define NO_VAR_FUNC(...) 5
|
|
#define VAR_FUNC(...) func(__VA_ARGS__);
|
|
#define VAR_PRINTF(str, ...) printf(str, __VA_ARGS__);
|
|
#ifdef PEDANTIC
|
|
// expected-warning@-4{{variadic macros are a Clang extension in OpenCL}}
|
|
// expected-warning@-4{{variadic macros are a Clang extension in OpenCL}}
|
|
// expected-warning@-4{{variadic macros are a Clang extension in OpenCL}}
|
|
#endif
|
|
|
|
int printf(__constant const char *st, ...);
|
|
|
|
void foo(void) {
|
|
NO_VAR_FUNC(1, 2, 3);
|
|
VAR_FUNC(1, 2, 3); // expected-error {{use of undeclared identifier 'func'}}
|
|
VAR_PRINTF("%i", 1);
|
|
}
|