Files
RedBear-OS/local/recipes/dev/libclc/source/clang/test/CodeGen/fixup-depth-overflow.c
T
vasilito cb424d7448 build: static patch-sanity linter (shift-left the malformed-patch class)
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).
2026-08-01 05:13:02 +03:00

29 lines
774 B
C

// RUN: %clang_cc1 -O1 -disable-llvm-passes -emit-llvm -o - %s | FileCheck %s
#define M if (x) goto L1;
#define M10 M M M M M M M M M M
#define M100 M10 M10 M10 M10 M10 M10 M10 M10 M10 M10
#define M1000 M100 M100 M100 M100 M100 M100 M100 M100 M100 M100
void f(int x) {
int h;
// Many gotos to not-yet-emitted labels would cause EHScope's FixupDepth
// to overflow (PR23490).
M1000 M1000 M1000
if (x == 5) {
// This will cause us to emit a clean-up of the stack variable. If the
// FixupDepths are broken, fixups will erroneously get threaded through it.
int i;
}
L1:
return;
}
// CHECK-LABEL: define {{(dso_local )?}}void @f
// CHECK-NOT: cleanup
// CHECK: {{^!0 = }}
// We might see 'cleanup' as part of a pathname or versioning in metadata