vgsp-sema: forwarding owns the release when a candidate is captured (ISSUE-0002)

r65 showed the operand-hold release gate must not run before the
forwarding gate: for a GR launch push whose software operand was
pending, the operand hold applied the launch-completion release as soon
as the software op ran, so the client passed the launch-completion wait
while the physical launch was still in flight; when the physical launch
later timed out (qmd_rel stuck at 5, want 6) the client read zeros
(MAIL bad).

Order the release sites fwd-first: when a forwarding candidate is
captured, drop any operand-hold record for the entry (the fwd record set
carries the same release) and record into the fwd set so the hardware
completion (or its bounded fallback) is the single delivery edge. The
operand hold keeps owning the release only when no candidate is
captured, exactly as r62 intended.

0 files changed, 0 insertions, 0 deletions