vasilito
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).
39 lines
686 B
Fortran
39 lines
686 B
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1
|
|
! C1134 A CYCLE statement must be within a DO construct
|
|
!
|
|
! C1166 An EXIT statement must be within a DO construct
|
|
|
|
subroutine s1()
|
|
! this one's OK
|
|
do i = 1,10
|
|
cycle
|
|
end do
|
|
|
|
! this one's OK
|
|
do i = 1,10
|
|
exit
|
|
end do
|
|
|
|
! all of these are OK
|
|
outer: do i = 1,10
|
|
cycle
|
|
inner: do j = 1,10
|
|
cycle
|
|
end do inner
|
|
cycle
|
|
end do outer
|
|
|
|
!ERROR: No matching DO construct for CYCLE statement
|
|
cycle
|
|
|
|
!ERROR: No matching construct for EXIT statement
|
|
exit
|
|
|
|
!ERROR: No matching DO construct for CYCLE statement
|
|
if(.true.) cycle
|
|
|
|
!ERROR: No matching construct for EXIT statement
|
|
if(.true.) exit
|
|
|
|
end subroutine s1
|