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).
18 lines
773 B
Plaintext
18 lines
773 B
Plaintext
# Test that BOLT can handle CIE's produced by GNU as. On RISC-V, GNU as produces
|
|
# the following initial instruction:
|
|
# DW_CFA_def_cfa_register: r2
|
|
# While I believe it is technically incorrect to use this instruction without
|
|
# first using a DW_CFA_def_cfa (since the offset is unspecified), both readelf
|
|
# and llvm-dwarfdump accept this and implicitly set the offset to 0.
|
|
# In BOLT, this used to trigger an assert, however, since it (correctly)
|
|
# believed the offset was not set. This test checks we can handle this
|
|
# situation.
|
|
|
|
RUN: yaml2obj -o %t %p/Inputs/cie-gnu.yaml
|
|
RUN: llvm-bolt -o %t.bolt %t --reorder-blocks=reverse
|
|
RUN: llvm-dwarfdump --debug-frame %t.bolt | FileCheck %s
|
|
|
|
CHECK: 0x400000: CFA=X2
|
|
CHECK: 0x400004: CFA=X2: X5=undefined
|
|
CHECK: 0x400006: CFA=X2
|