|
From: Christopher B. <cb...@co...> - 2014-08-23 18:29:00
|
Thanks Steve, We are definitely going to continue to use iverilog in the class. We will just come up with some work arounds to enable us to gradually leverage SV support in iverilog as it develops. Thanks for all of your (and the rest of the iverilog contributors) hard work on iverilog -- I am a big fan of using opensource tools in undergraduate education, so it is nice to have access to such a full-featured opensource verilog simulator. Best, Chris > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I don't think we support dumping things like structs broken > out. They show up in the trace in packed form. Sorry. > > The other thing on your list that is not supported is interfaces. > That is on my list of things to be addressed eventually, but I > (personally) have other more pressing things in front of it. > > It'd be awesome if you choose to use iverilog in your class, > we'll do what we can to support. > > On 08/23/2014 06:55 AM, Christopher Batten wrote: > > > > This is great info -- I think we will definitely move to FST. I > > guess I am still wondering if iverilog supports dumping the > > hierarchy in structs (and interfaces). Maybe one of the iverilog > > developers can chime in? > > > > It is not a show stopper. We can create little helper modules that > > take the struct on an input port essentially "break out" the fields > > internally. We can then liberally instantiate these for debugging > > purposes ... but of course this is less convenient. > > - -- > Steve Williams "The woods are lovely, dark and deep. > steve at icarus.com But I have promises to keep, > > http://www.icarus.com > and lines to code before I sleep, > > http://www.picturel.com > And lines to code before I sleep." > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iEYEARECAAYFAlP4qxEACgkQrPt1Sc2b3ikz8ACgji2UWkV5Dar6Vzja65CYr2Sl > YM4AoL7CZCV3n5FTsj0Dn0i0mDYd++Cx > =h3W8 > -----END PGP SIGNATURE----- |