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

36 lines
859 B
Fortran

! RUN: %python %S/test_errors.py %s %flang_fc1 -funderscoring
subroutine conflict1()
end subroutine
!ERROR: BIND(C) procedure assembly name conflicts with non BIND(C) procedure assembly name
subroutine foo(x) bind(c, name="conflict1_")
real :: x
end subroutine
subroutine no_conflict1() bind(c, name="")
end subroutine
subroutine foo2() bind(c, name="conflict2_")
end subroutine
subroutine bar()
interface
subroutine no_conflict1() bind(c, name="")
end subroutine
! ERROR: Non BIND(C) procedure assembly name conflicts with BIND(C) procedure assembly name
subroutine conflict2()
end subroutine
end interface
call no_conflict1()
call conflict2
end subroutine
subroutine no_conflict2() bind(c, name="no_conflict2_")
end subroutine
subroutine _()
end subroutine
subroutine dash_no_conflict() bind(c, name="")
end subroutine