Files
RedBear-OS/local/recipes/dev/libclc/source/flang/docs/OpenACC.md
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

1.7 KiB
Raw Blame History

OpenACC in Flang

---
local:
---

Intentional deviation from the specification

  • The end directive for combined construct can omit the loop keyword.
  • An !$acc routine with no parallelism clause is treated as if the seq clause was present.
  • !$acc end loop does not trigger a parsing error and is just ignored.
  • The restriction on !$acc data required clauses is emitted as a portability warning instead of an error as other compiler accepts it.
  • The if clause accepts scalar integer expression in addition to scalar logical expression.
  • !$acc routine directive can be placed at the top level.
  • !$acc cache directive accepts scalar variable.
  • The !$acc declare directive accepts assumed size array arguments for deviceptr and present clauses.
  • The OpenACC specification disallows a variable appearing multiple times in clauses of !$acc declare directives for a function, subroutine, program, or module, but it is allowed with a warning when same clause is used.

Remarks about incompatibilities with other implementations

  • Array element references in the data clauses are equivalent to array sections consisting of this single element, i.e. copyin(a(n)) is equivalent to copyin(a(n:n)). Some other implementations have treated it as copyin(a(:n)), which does not correspond to OpenACC spec Flang does not support this interpretation of an array element reference.