Files
RedBear-OS/local/recipes/dev/libclc/source/flang/test/Semantics/modfile79.F90
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

35 lines
766 B
Fortran

!RUN: rm -rf %t && mkdir -p %t
!RUN: %flang -c -DWHICH=1 -J%t %s && FileCheck %s <%t/modfile79a.mod && %flang -c -fhermetic-module-files -DWHICH=2 -J%t %s && %flang -c -J%t %s && FileCheck %s <%t/modfile79a.mod
!Ensure that writing modfile79c.mod doesn't cause a spurious
!regeneration of modfile79a.mod from its copy in the hermetic
!module file modfile79b.mod.
!CHECK: !mod$ v1 sum:93ec75fe672c5b6c
!CHECK-NEXT: module modfile79a
#if WHICH == 1
module modfile79a
interface foo
module procedure foo
end interface
contains
subroutine foo
end
end
#elif WHICH == 2
module modfile79b
use modfile79a
interface bar
procedure foo
end interface
end
#else
module modfile79c
use modfile79b
contains
subroutine test
call bar
end
end
#endif