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).
20 lines
785 B
C
20 lines
785 B
C
// RUN: %clang -target x86_64-unknown-linux-gnu -S -emit-llvm -o - -fsanitize=address %s | FileCheck %s
|
|
|
|
// Ensure that ASan properly instruments a load into a global where the index
|
|
// happens to be within the padding after the global which is used for the
|
|
// redzone.
|
|
|
|
// This global is 400 bytes long, but gets padded with 112 bytes for redzones,
|
|
// rounding the total size after instrumentation to 512.
|
|
int global_array[100] = {-1};
|
|
|
|
// This access is 412 bytes after the start of the global: past the end of the
|
|
// uninstrumented array, but within the bounds of the extended instrumented
|
|
// array. We should ensure this is still instrumented.
|
|
int main(void) { return global_array[103]; }
|
|
|
|
// CHECK: @main
|
|
// CHECK-NEXT: entry:
|
|
// CHECK: call void @__asan_report_load4
|
|
// CHECK: }
|