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
22 lines
435 B
C
22 lines
435 B
C
// RUN: %clang_cc1 -fsyntax-only -verify -pedantic %s
|
|
_Complex double X;
|
|
void test1(int c) {
|
|
X = 5;
|
|
}
|
|
void test2() {
|
|
int i;
|
|
double d = i;
|
|
double _Complex a = 5;
|
|
|
|
test1(a);
|
|
a = 5;
|
|
d = i;
|
|
}
|
|
int test3() {
|
|
int a[2];
|
|
a[0] = test3; // expected-warning{{incompatible pointer to integer conversion assigning to 'int' from 'int ()'}}
|
|
return 0;
|
|
}
|
|
short x; void test4(char c) { x += c; }
|
|
int y; void test5(char c) { y += c; }
|