Files
RedBear-OS/local/recipes/dev/libclc/source/clang/test/CodeGen/branch-target-layout.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

41 lines
885 B
C

// RUN: %clang_cc1 %s -O3 -emit-llvm -o - | FileCheck %s
//
// PR13214
// No assumption may be made about the order that a frontend emits branch
// targets (basic blocks). However, the backend's basic block layout makes an
// attempt to preserve source order of control flow, and any bias toward source
// order must start with the frontend.
//
// Note that the frontend inverts branches to simplify the condition, so the
// order of a branch instruction's labels cannot be used as a source order bias.
void calla(void);
void callb(void);
void callc(void);
// CHECK: @test1
// CHECK: @calla
// CHECK: @callb
// CHECK: @callc
// CHECK: ret void
void test1(int a) {
if (a)
calla();
else
callb();
callc();
}
// CHECK: @test2
// CHECK: @callb
// CHECK: @calla
// CHECK: @callc
// CHECK: ret void
void test2(int a) {
if (!a)
callb();
else
calla();
callc();
}