llvm-project/clang/test/Sema/function-ptr.c

// RUN: %clang_cc1 %s -verify -pedantic
typedef int unary_int_func(int arg);
unary_int_func *func;

unary_int_func *set_func(void *p) {
 func = p; // expected-warning {{converts between void pointer and function pointer}}
 p = func; // expected-warning {{converts between void pointer and function pointer}}

 return p; // expected-warning {{converts between void pointer and function pointer}}
}
Update tests to use %clang_cc1 instead of 'clang-cc' or 'clang -cc1'. - This is designed to make it obvious that %clang_cc1 is a "test variable" which is substituted. It is '%clang_cc1' instead of '%clang -cc1' because it can be useful to redefine what gets run as 'clang -cc1' (for example, to set a default target). llvm-svn: 91446 2009-12-16 04:14:24 +08:00			`// RUN: %clang_cc1 %s -verify -pedantic`
give better diagnostics for converting between function pointer and void*. llvm-svn: 45556 2008-01-04 06:56:36 +08:00			`typedef int unary_int_func(int arg);`
			`unary_int_func *func;`

			`unary_int_func set_func(void p) {`
Improve diagnostics when we fail to convert from a source type to a 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 2010-04-09 08:35:39 +08:00			`func = p; // expected-warning {{converts between void pointer and function pointer}}`
			`p = func; // expected-warning {{converts between void pointer and function pointer}}`
give better diagnostics for converting between function pointer and void*. llvm-svn: 45556 2008-01-04 06:56:36 +08:00
Improve diagnostics when we fail to convert from a source type to a 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 2010-04-09 08:35:39 +08:00			`return p; // expected-warning {{converts between void pointer and function pointer}}`
give better diagnostics for converting between function pointer and void*. llvm-svn: 45556 2008-01-04 06:56:36 +08:00			`}`