You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has been pointed out to me that exporting strings in VCD files is not actually part of the VCD file format (as defined by Verilog 2005). For example, see ghdl/ghdl#647
Would it be acceptable to add an (off by default) flag to the VCD writer to only export a standards compliant VCD file? So the VCD data can be used more broadly in applications that do not support string types.
The text was updated successfully, but these errors were encountered:
Unfortunately, there is no such thing as "standards compliant VCD"; only "VCD that people want to feed to tools they use". For example, CXXRTL used to export completely "standards compliant VCD", which crashed GTKWave, and this had to be fixed (in an incredibly awkward way) in this PR: YosysHQ/yosys#2881.
The closest thing to what you're asking that actually makes sense to implement is "VCD dialects" (so a GTKWave dialect, a Sigrok dialect, and so on), but I'm unconvinced that this is worth the effort.