-
Applied to git master.
2010-01-06 21:54:07 UTC by stevewilliams
-
I'm not planning on applying this to the v0_9 branch because I don't intend to include the changes that led to the need for these patches.
2010-01-06 21:54:07 UTC by stevewilliams
-
Applied to git master.
2010-01-06 21:49:07 UTC by stevewilliams
-
Applied to git master.
2010-01-06 21:45:44 UTC by stevewilliams
-
This should be applied to V0.9 if the patch that caused this is also ported to V0.9.
2010-01-06 21:43:52 UTC by caryr
-
The recent patch in the vpi directory added a C++ .o file. Some systems require that this be linked with the C++ compiler. I'm also including a patch that make the C++ compilation us the CXXFLAGS variable instead of CFALGS.
2010-01-06 21:42:37 UTC by caryr
-
This was causing my circuit test code to fail. The issue is that the select not the signal determine if the select is sign padded or not. This patch fixes this for signal selects that start at the beginning of the vector (it used to pad based on the signal) and adds the capability to sign pad expressions when the select is not at the beginning (it used to always zero pad).
This needs to be...
2010-01-06 20:03:20 UTC by caryr
-
the vpi_get_vlog_info() call is supposed to return the version information for the simulator. This patch makes this work correctly using our current scheme for the version.
This needs to be applied to both development and V0.9. I have a test that verifies the $simparam() and vpi_get_vlog_info() both return the same basic information, but I'm waiting for the test suite to get tagged for the...
2010-01-03 02:31:03 UTC by caryr
-
I was thinking about this a bit today and thought that $monitor like the dumpers could also have this same issue. I coded a simple example to test this and yes it does have the same issue. I also currently have access to a commercial simulator and it did not run the $monitor when I was not expecting it to. I am attaching the code here, raising the priority and changing the summary.
2010-01-02 02:13:01 UTC by caryr
-
Priority +1 because this generates incorrect results without error or warning. It is easy to work around, simply declare effected nets explicitly.
2010-01-01 01:07:04 UTC by stevewilliams
