vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
78 lines
2.4 KiB
C
78 lines
2.4 KiB
C
// RUN: %clang_cc1 %s -verify -fsyntax-only
|
|
|
|
void a(void) {
|
|
__complex__ int arr;
|
|
__complex__ short brr;
|
|
__complex__ unsigned xx;
|
|
__complex__ signed yy;
|
|
__complex__ int result;
|
|
int ii;
|
|
int aa = 1 + 1.0iF;
|
|
int bb = 0;
|
|
bb += 1i;
|
|
|
|
typedef __complex__ float ComplexFloat;
|
|
int cc = 1 + (ComplexFloat)(1.0iF);
|
|
|
|
result = arr*ii;
|
|
result = ii*brr;
|
|
|
|
result = arr*brr;
|
|
result = xx*yy;
|
|
|
|
switch (arr) { // expected-error{{statement requires expression of integer type ('_Complex int' invalid)}}
|
|
case brr: ; // expected-error{{integer constant expression must have integer type}}
|
|
case xx: ; // expected-error{{integer constant expression must have integer type}}
|
|
}
|
|
switch (ii) {
|
|
case brr: ; // expected-error{{integer constant expression must have integer type}}
|
|
case xx: ; // expected-error{{integer constant expression must have integer type}}
|
|
}
|
|
}
|
|
|
|
void Tester(void) {
|
|
__complex short a1;
|
|
__complex int a2;
|
|
__complex float a3;
|
|
__complex double a4;
|
|
short a5;
|
|
int a6;
|
|
float a7;
|
|
double a8;
|
|
#define TestPair(m,n) int x##m##n = a##m+a##n;
|
|
#define TestPairs(m) TestPair(m,1) TestPair(m,2) \
|
|
TestPair(m,3) TestPair(m,4) \
|
|
TestPair(m,5) TestPair(m,6) \
|
|
TestPair(m,7) TestPair(m,8)
|
|
TestPairs(1); TestPairs(2);
|
|
TestPairs(3); TestPairs(4);
|
|
TestPairs(5); TestPairs(6);
|
|
TestPairs(7); TestPairs(8);
|
|
}
|
|
|
|
void test3(_Complex int *x) {
|
|
*x = ~*x;
|
|
}
|
|
|
|
void test4(_Complex float *x) {
|
|
*x = ~*x;
|
|
}
|
|
|
|
void test5(_Complex int *x) {
|
|
(*x)++;
|
|
}
|
|
|
|
// None of these array bounds is an ICE due to the use of literals of
|
|
// non-integer type. But we can constant-fold all of them.
|
|
int i1[(2+3i)*(5+7i) == 29i-11 ? 1 : -1]; // expected-warning {{fold}}
|
|
int i2[(29i-11)/(5+7i) == 2+3i ? 1 : -1]; // expected-warning {{fold}}
|
|
int i3[-(2+3i) == +(-3i-2) ? 1 : -1]; // expected-warning {{fold}}
|
|
int i4[~(2+3i) == 2-3i ? 1 : -1]; // expected-warning {{fold}}
|
|
int i5[(3i == -(-3i) ? ((void)3, 1i - 1) : 0) == 1i - 1 ? 1 : -1]; // expected-warning {{fold}}
|
|
|
|
int f1[(2.0+3.0i)*(5.0+7.0i) == 29.0i-11.0 ? 1 : -1]; // expected-warning {{fold}}
|
|
int f2[(29.0i-11.0)/(5.0+7.0i) == 2.0+3.0i ? 1 : -1]; // expected-warning {{fold}}
|
|
int f3[-(2.0+3.0i) == +(-3.0i-2.0) ? 1 : -1]; // expected-warning {{fold}}
|
|
int f4[~(2.0+3.0i) == 2.0-3.0i ? 1 : -1]; // expected-warning {{fold}}
|
|
int f5[(3.0i == -(-3.0i) ? ((void)3.0, __extension__ (1.0i - 1.0)) : 0) == 1.0i - 1.0 ? 1 : -1]; // expected-warning {{fold}}
|