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).
13 lines
740 B
Common Lisp
13 lines
740 B
Common Lisp
// RUN: %clang_cc1 -O0 -cl-std=CL2.0 -fsyntax-only -verify %s
|
|
|
|
global atomic_int a1 = 0;
|
|
|
|
kernel void test_atomic_initialization() {
|
|
a1 = 1; // expected-error {{atomic variable can be assigned to a variable only in global address space}}
|
|
atomic_int a2 = 0; // expected-error {{atomic variable can be initialized to a variable only in global address space}}
|
|
private atomic_int a3 = 0; // expected-error {{atomic variable can be initialized to a variable only in global address space}}
|
|
local atomic_int a4 = 0; // expected-error {{'__local' variable cannot have an initializer}}
|
|
global atomic_int a5 = 0; // expected-error {{function scope variable cannot be declared in global address space}}
|
|
static global atomic_int a6 = 0;
|
|
}
|