7068aa9841
Clang has traditionally allowed C programs to implicitly convert integers to pointers and pointers to integers, despite it not being valid to do so except under special circumstances (like converting the integer 0, which is the null pointer constant, to a pointer). In C89, this would result in undefined behavior per 3.3.4, and in C99 this rule was strengthened to be a constraint violation instead. Constraint violations are most often handled as an error. This patch changes the warning to default to an error in all C modes (it is already an error in C++). This gives us better security posture by calling out potential programmer mistakes in code but still allows users who need this behavior to use -Wno-error=int-conversion to retain the warning behavior, or -Wno-int-conversion to silence the diagnostic entirely. Differential Revision: https://reviews.llvm.org/D129881
28 lines
878 B
Objective-C
28 lines
878 B
Objective-C
// Test this without pch.
|
|
// RUN: %clang_cc1 -fblocks -include %S/objc_exprs.h -fsyntax-only -verify %s
|
|
|
|
// Test with pch.
|
|
// RUN: %clang_cc1 -x objective-c-header -emit-pch -fblocks -o %t %S/objc_exprs.h
|
|
// RUN: %clang_cc1 -fblocks -include-pch %t -fsyntax-only -verify %s
|
|
|
|
// Expressions
|
|
int *A1 = (objc_string)0; // expected-warning {{aka 'NSString *'}}
|
|
|
|
char A2 = (objc_encode){}; // expected-error {{not a compile-time constant}} \
|
|
expected-error {{char[2]}}
|
|
|
|
int *A3 = (objc_protocol)0; // expected-warning {{aka 'Protocol *'}}
|
|
|
|
|
|
// Types.
|
|
int *T0 = (objc_id_protocol_ty)0; // expected-warning {{aka 'id<foo>'}}
|
|
|
|
int *T1 = (objc_interface_ty)0; // expected-warning {{aka 'itf *'}}
|
|
int *T2 = (objc_qual_interface_ty)0; // expected-warning {{aka 'itf<foo> *'}}
|
|
|
|
objc_selector_noArgs s1;
|
|
objc_selector_oneArg s2;
|
|
objc_selector_twoArg s3;
|
|
|
|
|