Back to Signal Feed
CodeTracked since May 19, 2026

Force herdr’s vendored libghostty-vt build to use baseline CPU

This PR changes herdr’s vendored libghostty-vt Zig build to compile with a baseline CPU target so the nested `zig build` no longer emits instructions from the build host that can crash on older x86_64 machines.

herdrlibghostty-vtZigbuild.rs

What Happened

  • This PR changes herdr’s vendored libghostty-vt Zig build to compile with a baseline CPU target so the nested `zig build` no longer emits instructions from the build host that can crash on older x86_64 machines.
  • This PR changes herdr’s vendored libghostty-vt Zig build to compile with a baseline CPU target so the nested `zig build` no longer emits instructions from the build host that can crash on older x86_64 machines.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Added an explicit compatibility safeguard in the nested Zig invocation by setting `-Dcpu=baseline` for vendored libghostty-vt, and retained the current `-Dtarget` handling needed for sandboxed source builds, changing the package’s effective binary output ABI behavior across x86_64 targets.

Why Track This

Why It Matters

Operators using this package on Linux are less likely to see `SIGILL` startup failures when deployments run on slower or older x86_64 CPUs, so they can avoid per-host pinning or emergency rollbacks for apparently random crashes. This is implemented by forcing baseline-codegen in the vendored Zig build path used by `herdr`, and teams should still watch for regressions when the vendored library or Zig compiler defaults change so host-feature leakage does not reappear.

Impact

Operators using this package on Linux are less likely to see `SIGILL` startup failures when deployments run on slower or older x86_64 CPUs, so they can avoid per-host pinning or emergency rollbacks for apparently random crashes. This is implemented by forcing baseline-codegen in the vendored Zig build path used by `herdr`, and teams should still watch for regressions when the vendored library or Zig compiler defaults change so host-feature leakage does not reappear.

What To Watch Next

  • Watch whether herdr becomes a repeated pattern.
  • Track follow-up changes around LLMOps.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: nested_zig_build_default_cpu_feature_drift, future_zig_codegen_default_changes.
Open Topic TimelineOpen Technical EventOpen Original Sourcenested_zig_build_default_cpu_feature_drift / future_zig_codegen_default_changes / libghostty_vt_update_compatibility_regression

Supporting Evidence