Dump hierarchy block before first value change - #13
Open
johnjohnlin wants to merge 1 commit into
Open
johnjohnlin wants to merge 1 commit into
johnjohnlin wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR tries to resolve verilator/verilator#7990 in verilator. Existing
fstapi.cdump hierarchy block upon simulation is finished, and the hierarchy block is write as an independent hier file. However, current libfstwriter implementation just store in-memory, so a failed simulation (segmentation fault, verilog/C++ assertion error) cannot view the hierarchy.This only involves 3 lines of changes in libfstwriter. To keep the bit-trueness, I moved the order of the original
fstapi.cto match the behavior (just moved, not modified).