================
@@ -0,0 +1,103 @@
+// RUN: %clang_cc1 -Wchar-subscripts -fsyntax-only -verify %s
+
+void t1(void) {
+ int array[1] = { 0 };
+ char subscript = 0;
+ int val = array[subscript]; // expected-warning{{array subscript is of type
'char'}}
+}
+
+void t2(void) {
+ int array[1] = { 0 };
+ char subscript = 0;
+ int val = subscript[array]; // expected-warning{{array subscript is of type
'char'}}
+}
+
+void t3(void) {
+ int *array = 0;
+ char subscript = 0;
+ int val = array[subscript]; // expected-warning{{array subscript is of type
'char'}}
+}
+
+void t4(void) {
+ int *array = 0;
+ char subscript = 0;
+ int val = subscript[array]; // expected-warning{{array subscript is of type
'char'}}
+}
+
+char returnsChar(void);
+void t5(void) {
+ int *array = 0;
+ int val = array[returnsChar()]; // expected-warning{{array subscript is of
type 'char'}}
+}
+
+void t6(void) {
+ int array[1] = { 0 };
+ signed char subscript = 0;
+ int val = array[subscript]; // no warning for explicit signed char
----------------
wheatman wrote:
That is an interesting questions, the behavior for that was not changed.
The current behavior for explicitly signed or unsigned chars is to have no
warning, only unspecified chars have warnings.
https://godbolt.org/z/7oc3ET4h4
https://github.com/llvm/llvm-project/pull/69061
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
