> Hello Tristan, > < as GHW is a binary format, there is not grammar for it. You have to > look at the sources to understand the format. I am not sure that > a grammar is the best way to describe this format (for the same > reason, I suppose no one has written a grammar for mp3). > /> > > > I have just begun to sift through some of GHDL's sources. I believe > ghwlib.c is the place to start?
Yes: ghwlib.c, ghwdump.c and get-waves.adb The format isn't very complex: there are a sections to describe strings, types, hierarchy. And there are sections for snapshot and delta changes (cycle). > Perhaps you are right that since GHW is a binary format, describing > it in (E)BNF would not be possible. However, do you think you could > come up with something like a frame format describing where the data > boundaries are (e.g. preamble, header, payload, footer, or something > of this sort)? > > < GHW supports all the vhdl types, including floating point types. > /> > > > This is what I like about GHW, since the format is VHDL-friendly. Yes, that's the whole purpose of this format! > I'm not familiar with the FST and HDF formats. Who / which tool uses > these currently? A quick check on Google regarding FST did not seem > to return meaningful results. The main advantage of FST, VZT and other gtkwave formats is the compression level. Tristan. _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
