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
38 lines
866 B
C
38 lines
866 B
C
// RUN: %clang_cc1 -fsyntax-only -verify -pedantic %s
|
|
|
|
char *funk(int format);
|
|
enum Test {A=-1};
|
|
char *funk(enum Test x);
|
|
|
|
int eli(float b); // expected-note {{previous declaration is here}}
|
|
int b(int c) {return 1;}
|
|
|
|
int foo();
|
|
int foo() {
|
|
int eli(int (int)); // expected-error {{conflicting types for 'eli'}}
|
|
eli(b); // expected-error{{passing 'int (int)' to parameter of incompatible type 'float'}}
|
|
return 0;
|
|
}
|
|
|
|
int bar();
|
|
int bar(int i) // expected-note {{previous definition is here}}
|
|
{
|
|
return 0;
|
|
}
|
|
int bar() // expected-error {{redefinition of 'bar'}}
|
|
{
|
|
return 0;
|
|
}
|
|
|
|
int foobar(int); // note {{previous declaration is here}}
|
|
int foobar() // error {{conflicting types for 'foobar'}}
|
|
{
|
|
return 0;
|
|
}
|
|
|
|
int wibble(); // expected-note {{previous declaration is here}}
|
|
float wibble() // expected-error {{conflicting types for 'wibble'}}
|
|
{
|
|
return 0.0f;
|
|
}
|