Files
RedBear-OS/local/recipes/dev/libclc/source/lld/test/MachO/chained-fixups-empty.s
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

25 lines
815 B
ArmAsm

# REQUIRES: x86
# RUN: llvm-mc -filetype=obj -triple=x86_64-apple-darwin %s -o %t.o
# RUN: %lld -dylib -fixup_chains -o %t %t.o
# RUN: llvm-objdump --macho --all-headers %t | FileCheck %s
## dyld always expects LC_DYLD_CHAINED_FIXUPS to point to a valid
## chained fixups header, even if there aren't any fixups.
# CHECK: cmd LC_DYLD_CHAINED_FIXUPS
# CHECK-NEXT: cmdsize 16
# CHECK-NEXT: dataoff [[#]]
# CHECK-NEXT: datasize 48
## While ld64 emits the root trie node even if there are no exports,
## setting the data size and offset to zero works too in practice.
# CHECK: cmd LC_DYLD_EXPORTS_TRIE
# CHECK-NEXT: cmdsize 16
# CHECK-NEXT: dataoff 0
# CHECK-NEXT: datasize 0
## Old load commands should not be generated.
# CHECK-NOT: cmd LC_DYLD_INFO_ONLY
_not_exported:
.space 1