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).
21 lines
949 B
Fortran
21 lines
949 B
Fortran
! Verify that the driver correctly processes `-fsyntax-only`.
|
|
!
|
|
! By default, the compiler driver (`flang`) will create actions/phases to
|
|
! generate machine code (i.e. object files). The `-fsyntax-only` flag is a
|
|
! "phase-control" flag that controls this behavior and makes the driver stop
|
|
! once the semantic checks have been run. The frontend driver (`flang -fc1`)
|
|
! runs `-fsyntax-only` by default (i.e. that's the default action), so the flag
|
|
! can be skipped.
|
|
|
|
! RUN: %flang -fsyntax-only %s 2>&1 | FileCheck %s --allow-empty
|
|
! RUN: %flang_fc1 %s 2>&1 | FileCheck %s --allow-empty
|
|
|
|
! RUN: rm -rf %t/non-existent-dir/
|
|
! RUN: not %flang -c %s -o %t/non-existent-dir/syntax-only.o 2>&1 | FileCheck %s --check-prefix=NO_FSYNTAX_ONLY
|
|
! RUN: not %flang_fc1 -emit-obj %s -o %t/non-existent-dir/syntax-only.o 2>&1 | FileCheck %s --check-prefix=NO_FSYNTAX_ONLY
|
|
|
|
! CHECK-NOT: error
|
|
! NO_FSYNTAX_ONLY: error: failed to create the output file
|
|
|
|
end program
|