131e878664
This improves diagnostic (& important to me, DWARF) accuracy - otherwise there could be ambiguities between "std::nullptr_t" and some user-defined type that's /actually/ "nullptr_t" defined in the global namespace. Differential Revision: https://reviews.llvm.org/D110044
21 lines
889 B
C
21 lines
889 B
C
// RUN: %clang_cc1 -fsyntax-only -verify -Wno-format -Wformat-pedantic %s
|
|
// RUN: %clang_cc1 -xobjective-c -fblocks -fsyntax-only -verify -Wno-format -Wformat-pedantic %s
|
|
// RUN: %clang_cc1 -xc++ -fsyntax-only -verify -Wno-format -Wformat-pedantic %s
|
|
|
|
__attribute__((format(printf, 1, 2)))
|
|
int printf(const char *restrict, ...);
|
|
|
|
int main() {
|
|
printf("%p", (int *)0); // expected-warning {{format specifies type 'void *' but the argument has type 'int *'}}
|
|
printf("%p", (void *)0);
|
|
|
|
#ifdef __OBJC__
|
|
printf("%p", ^{}); // expected-warning {{format specifies type 'void *' but the argument has type 'void (^)(void)'}}
|
|
printf("%p", (id)0); // expected-warning {{format specifies type 'void *' but the argument has type 'id'}}
|
|
#endif
|
|
|
|
#ifdef __cplusplus
|
|
printf("%p", nullptr); // expected-warning {{format specifies type 'void *' but the argument has type 'std::nullptr_t'}}
|
|
#endif
|
|
}
|