claude-noether
f203b70f4f
Audit during ohm pkgrel=4 migration found the per-series -danctnix mirrors merged in #17 do NOT apply against the linux-pinetab2 baseline: all 17 of them use DKMS-style root paths (bes2600/foo.c) rather than in-tree staging paths (drivers/staging/bes2600/foo.c), and at least one has a corrupted mixed-prefix header (a/drivers/staging/bes2600/... b/bes2600/...). ka-promote ohm with those includes produced a 172 644-byte cumulative touching 27 file paths, of which 11 are bogus. The hand-curated 0001-bes2600-besser-cumulative-series.patch from the working danctnix-besser-pkgbuild flow on boltzmann (148 149 bytes, 48 in-tree staging files) is what pkgrel=3 actually builds with. Until the per-series mirrors are reconstructed (followup issue to be opened separately), the bes2600 driver scope is satisfied here by staging that hand-curated cumulative as a single-file series-dir patches/driver/bes2600/cumulative-c5x-danctnix/. ohm.yaml drops the broken per-series includes in favour of: - driver/bes2600/cumulative-c5x-danctnix/ - driver/bes2600/scan-filter-5ghz-danctnix/ (closes besser#1) - arch/arm64/xor-neon-ffixed-x18-scs-build-fix-danctnix/ ka-promote ohm now produces a self-consistent 157 446-byte cumulative (148 149 + 7 735 + 1 562 = exact byte arithmetic) with b2sum a807297b25be... which is what the new marfrit-packages/arch/linux-pinetab2-danctnix-besser PKGBUILD pkgrel=4 pins. Also fixes fleet/ohm.yaml YAML parse error: bar5_burn_in had a scalar value followed by a sub-list, which ka-promote (PyYAML) refused to parse. The whole manifest had never parsed cleanly since #18 landed. Refs: #5 (migrate PKGBUILD), #2 (mirror besser series — needs per-series rewrite followup), besser#1 (Patch I).
21 lines
1.0 KiB
Markdown
21 lines
1.0 KiB
Markdown
# xor-neon-ffixed-x18-scs-build-fix-danctnix — GCC 15.2.1 build fix
|
|
|
|
Restores `-ffixed-x18` for `arch/arm64/lib/xor-neon.c` when
|
|
`CONFIG_SHADOW_CALL_STACK=y`. GCC 15.2.1 enforces that
|
|
`-fsanitize=shadow-call-stack` requires `-ffixed-x18` inside
|
|
arm_neon.h's `#pragma GCC target()` push/pop blocks; CC_FLAGS_REMOVE
|
|
strips the kernel-wide `-ffixed-x18` for xor-neon.o and CC_FLAGS_FPU
|
|
does not restore it.
|
|
|
|
**Note on current ohm config**: `linux-pinetab2-danctnix-besser`
|
|
config has `# CONFIG_SHADOW_CALL_STACK is not set` as of pkgrel=3,
|
|
which makes this patch a runtime no-op (`$(if $(CONFIG_SHADOW_CALL_STACK),
|
|
-ffixed-x18)` evaluates to nothing). Patch is kept in the manifest as
|
|
belt-and-suspenders for the day SCS gets re-enabled (tracked in
|
|
besser issue for GCC fix monitoring).
|
|
|
|
See [[reference_arm64_scs_arm_neon_gcc15]] for the full toolchain
|
|
analysis. This patch is the upstream-friendly Makefile fix; the
|
|
config-side `SHADOW_CALL_STACK=n` workaround is the immediate
|
|
runtime mitigation. Both are present in pkgrel=3 for safety.
|