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).
30 lines
673 B
Fortran
30 lines
673 B
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1
|
|
MODULE test
|
|
SAVE
|
|
CONTAINS
|
|
PURE FUNCTION pf( )
|
|
IMPLICIT NONE
|
|
INTEGER :: pf
|
|
INTEGER :: mc
|
|
!OK: SAVE statement is not inherited by the function
|
|
END FUNCTION
|
|
|
|
PURE FUNCTION pf2( )
|
|
IMPLICIT NONE
|
|
SAVE
|
|
INTEGER :: pf2
|
|
!ERROR: A pure subprogram may not have a variable with the SAVE attribute
|
|
INTEGER :: mc
|
|
END FUNCTION
|
|
|
|
! This same subroutine appears in test save02.f90 where it is not an
|
|
! error due to -fno-automatic.
|
|
SUBROUTINE foo
|
|
INTEGER, TARGET :: t
|
|
!ERROR: An initial data target may not be a reference to an object 't' that lacks the SAVE attribute
|
|
INTEGER, POINTER :: p => t
|
|
end
|
|
|
|
END MODULE
|
|
|