Cast reset value for transparent read ports to integer #454
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently if you pass a list of items which can be converted to an integer but are not integers (for example,
numpy.int64
objects), they are converted when used to initialiseMemory._array
, but a transparent read port sets its reset value tomem.init[0]
, which is not cast.This eventually causes VcdWriter to bomb out because it checks
isinstance(value, int)
which fails fornumpy.int64
.This PR uses
operator.index
to cast the value to an integer, the same way it's done inside the init setter when creatingMemory._array
.Test case:
Traceback: