Forced signals in FSDB dumps: when port aliases diverge, and when force is detectable (VCS measurements)
Measured on Synopsys VCS with Verdi's FSDB tooling, on small fixtures (56 runs).
1. The dump stores forced values for the directly forced signal, with or without force recording. A forced signal gets its own stored values even if it had none before. 2. Forced versus normally driven is visible ONLY when the dump was made with force recording enabled: Forced/Released markers on the target and its direct port name. Without it, value history alone can't distinguish a force from a normal drive. Apart from the markers, dump contents are identical either way. 3. Port aliases (the same connection under parent and child names): - A plain same-width wire: both sides are always equal, whichever side is forced. - One-way connections (a variable or expression driving an input; a variable output): forcing or depositing the RECEIVING side makes the two names differ until release (for a force) or until the next driver update (for a deposit). Forcing the driving side propagates. - Width-converting ports agree on the common low bits. 4. Values a viewer computes at read time show the forced effect but carry no force marker.
Implication for any FSDB converter or viewer that de-duplicates port aliases or computes unstored nets: don't assume alias equality for one-way connections when writes are possible. Use force markers when present.