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).
31 lines
935 B
LLVM
31 lines
935 B
LLVM
; RUN: opt %loadNPMPolly -passes=polly-codegen -S < %s | FileCheck %s
|
|
;
|
|
; llvm.org/PR25439
|
|
; The dominance of the generated non-affine subregion block was based on the
|
|
; scop's merge block, therefore resulted in an invalid DominanceTree.
|
|
; It resulted in some values as assumed to be unusable in the actual generated
|
|
; exit block. Here we check whether the value %escaping is taken from the
|
|
; generated block.
|
|
;
|
|
; CHECK-LABEL: polly.stmt.subregion_entry:
|
|
; CHECK: %p_escaping = select i1 undef, i32 undef, i32 undef
|
|
;
|
|
; CHECK-LABEL: polly.stmt.polly.merge_new_and_old.exit:
|
|
; CHECK: store i32 %p_escaping, ptr %escaping.s2a
|
|
|
|
define i32 @func() {
|
|
entry:
|
|
br label %subregion_entry
|
|
|
|
subregion_entry:
|
|
%escaping = select i1 undef, i32 undef, i32 undef
|
|
%cond = or i1 undef, undef
|
|
br i1 %cond, label %subregion_exit, label %subregion_if
|
|
|
|
subregion_if:
|
|
br label %subregion_exit
|
|
|
|
subregion_exit:
|
|
ret i32 %escaping
|
|
}
|