This catches places where a function without a prototype is accidentally used, potentially passing an incorrect number of arguments, and is a follow-up to the work done in https://reviews.llvm.org/D122895 and described in the RFC (https://discourse.llvm.org/t/rfc-enabling-wstrict-prototypes-by-default-in-c). The diagnostic is grouped under the new -Wdeprecated-non-prototypes warning group and is enabled by default. The diagnostic is disabled if the function being called was implicitly declared (the user already gets an on-by-default warning about the creation of the implicit function declaration, so no need to warn them twice on the same line). Additionally, the diagnostic is disabled if the declaration of the function without a prototype was in a location where the user explicitly disabled deprecation warnings for functions without prototypes (this allows the provider of the API a way to disable the diagnostic at call sites because the lack of prototype is intentional).
13 lines
479 B
C
13 lines
479 B
C
// RUN: %clang_analyze_cc1 -fblocks -analyzer-checker=core,nullability -Wno-deprecated-non-prototype -verify %s
|
|
|
|
void it_takes_two(int a, int b);
|
|
void function_pointer_arity_mismatch() {
|
|
void(*fptr)() = it_takes_two;
|
|
fptr(1); // no-crash expected-warning {{Function taking 2 arguments is called with fewer (1)}}
|
|
}
|
|
|
|
void block_arity_mismatch() {
|
|
void(^b)() = ^(int a, int b) { };
|
|
b(1); // no-crash expected-warning {{Block taking 2 arguments is called with fewer (1)}}
|
|
}
|