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).
26 lines
747 B
C++
26 lines
747 B
C++
// RUN: %clang_cc1 -triple armv7-apple-ios -emit-llvm -o - %s | FileCheck %s
|
|
struct Empty {};
|
|
|
|
Empty emptyvar;
|
|
|
|
int take_args(int a, ...) {
|
|
__builtin_va_list l;
|
|
__builtin_va_start(l, a);
|
|
// CHECK: call void @llvm.va_start
|
|
|
|
emptyvar = __builtin_va_arg(l, Empty);
|
|
// CHECK: load ptr, ptr
|
|
|
|
// It's conceivable that EMPTY_PTR may not actually be a valid pointer
|
|
// (e.g. it's at the very bottom of the stack and the next page is
|
|
// invalid). This doesn't matter provided it's never loaded (there's no
|
|
// well-defined way to tell), but it becomes a problem if we do try to use it.
|
|
// CHECK-NOT: load %struct.Empty, ptr {{%[a-zA-Z0-9._]+}}
|
|
|
|
int i = __builtin_va_arg(l, int);
|
|
// CHECK: load i32, ptr
|
|
|
|
__builtin_va_end(l);
|
|
return i;
|
|
}
|