Files
RedBear-OS/local/recipes/dev/libclc/source/llvm/test/Object/macho-rebase-bind-trailing-opcode-boundary.test
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

17 lines
790 B
Plaintext

RUN: yaml2obj %p/Inputs/MachO/rebase-bind-table-trailing-opcode.yaml | \
RUN: llvm-objdump --rebase --bind --weak-bind --macho - | \
RUN: FileCheck %s
CHECK: Rebase table:
CHECK-NEXT: segment section address type
CHECK-NEXT: __DATA_CONST __got 0x00008000 pointer
CHECK-NEXT: __DATA __la_symbol_ptr 0x0000C000 pointer
CHECK: Bind table:
CHECK-NEXT: segment section address type addend dylib symbol
CHECK-NEXT: __DATA_CONST __got 0x00008008 pointer 0 libSystem dyld_stub_binder
CHECK: Weak bind table:
CHECK-NEXT: segment section address type addend symbol
CHECK-NEXT: __DATA_CONST __got 0x00008000 pointer 0 _foo