c68e140657
destination type for initialization, assignment, parameter-passing,
etc. The main issue fixed here is that we used rather confusing
wording for diagnostics such as
t.c:2:9: warning: initializing 'char const [2]' discards qualifiers,
expected 'char *' [-pedantic]
char *name = __func__;
^ ~~~~~~~~
We're not initializing a 'char const [2]', we're initializing a 'char
*' with an expression of type 'char const [2]'. Similar problems
existed for other diagnostics in this area, so I've normalized them all
with more precise descriptive text to say what we're
initializing/converting/assigning/etc. from and to. The warning for
the code above is now:
t.c:2:9: warning: initializing 'char *' from an expression of type
'char const [2]' discards qualifiers [-pedantic]
char *name = __func__;
^ ~~~~~~~~
Fixes <rdar://problem/7447179>.
llvm-svn: 100832
16 lines
590 B
C
16 lines
590 B
C
// RUN: %clang_cc1 -analyze -analyzer-experimental-internal-checks -analyzer-check-objc-mem -Werror %s -analyzer-store=basic -verify
|
|
// RUN: %clang_cc1 -analyze -analyzer-experimental-internal-checks -analyzer-check-objc-mem -Werror %s -analyzer-store=region -verify
|
|
|
|
// This test case illustrates that using '-analyze' overrides the effect of
|
|
// -Werror. This allows basic warnings not to interfere with producing
|
|
// analyzer results.
|
|
|
|
char* f(int *p) {
|
|
return p; // expected-warning{{incompatible pointer types}}
|
|
}
|
|
|
|
void g(int *p) {
|
|
if (!p) *p = 0; // expected-warning{{null}}
|
|
}
|
|
|