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).
32 lines
651 B
Fortran
32 lines
651 B
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1 -pedantic
|
|
! test global name conflicts
|
|
|
|
subroutine ext1
|
|
end
|
|
|
|
subroutine ext2
|
|
!ERROR: Two entities have the same global name 'ext1'
|
|
common /ext1/ x
|
|
end
|
|
|
|
module ext4
|
|
contains
|
|
!ERROR: Two entities have the same global name 'ext2'
|
|
subroutine foo() bind(c,name="ext2")
|
|
end
|
|
!ERROR: Two entities have the same global name 'ext3'
|
|
subroutine bar() bind(c,name="ext3")
|
|
end
|
|
end
|
|
|
|
block data ext3
|
|
!PORTABILITY: Global name 'ext4' conflicts with a module [-Wbenign-name-clash]
|
|
common /ext4/ x
|
|
end
|
|
|
|
subroutine s
|
|
!ERROR: Two entities have the same global name 'foo'
|
|
common /foo/n
|
|
call foo
|
|
end
|