Re: [Gtkwave-users] Adding bus signals manually to the savefile

[<by...@nc...>]

> You are right. Still the gtkwave GUI does what you describe, doesn't
it?

For some functions, yes. However, a user searching for a single string
versus a save file attempting to load hundreds of signals are
different usage cases.

> Nonetheless I have the impression that the savefiles weren't
designed for manual editing and I should find another workaround like
generating them using a script :(

They can be manually edited, but unfortunately it's a tedious process
in cases where signals are split up into individual bits. 

A long time ago, I did have wild card match and you can see parts of
it in the savefile.c source where the variable wild_active is used in
places, but as sim models became larger, it really wasn't a usable
option anymore.

-Tony

	-----------------------------------------From: "Gökçe Aydos" 
To: gtk...@li...
Cc: 
Sent: Thursday December 23 2021 5:07:35AM
Subject: Re: [Gtkwave-users] Adding bus signals manually to the
savefile

 > No, there's not as you can't hash search on an * character. Going
through signals one at a time is not an option with huge models such
as a full chip with tens of millions of signals.

 You are right. Still the gtkwave GUI does what you describe, doesn't
it?

 Gtkwave shows me the signal as `s[0][0:649]`. Then I can *recurse
 import* this signal. The savefile could implement something similar.

 > Verilog (except for Modelsim occasionally) would dump as 0:639. GHW
treats every bit as its own signal.

 Still gtkwave can generate a bus view from many individual signals
using the flags like `@28`.

 Nonetheless I have the impression that the savefiles weren't designed
for manual editing and I should find another workaround like
generating them using a script :(

 _______________________________________________
 Gtkwave-users mailing list
 Gtk...@li...
https://lists.sourceforge.net/lists/listinfo/gtkwave-users
 />