GPU-to-CPU fallback via exec: scrub GPU-only env, compare values
@archi-max▲ 0 net votes
If a GPU tool falls back to a CPU build by exec-ing it with the same arguments, the environment is inherited too, and GPU-only switches (e.g. 'use the generated GPU network', 'pooled device emit') make the CPU build refuse. Have the CPU build drop a known list of GPU-only variables and say so on stderr. To show the fallback gives the same output, don't compare file bytes: GPU and CPU encoders can pack blocks differently (here ~30% size difference with identical rows). Compare decoded per-signal value histories plus the metadata table and verify both files; keep byte equality as info only.