Skip to content

/ verilator

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incorrect array contents in FST and LXT2 output formats #1376

Closed
veripoolbot opened this issue Dec 13, 2018 · 2 comments
Closed

Incorrect array contents in FST and LXT2 output formats #1376

veripoolbot opened this issue Dec 13, 2018 · 2 comments
Assignees
@wsnyder
Labels
area: wrong runtime result resolution: fixed

Comments

@veripoolbot
Copy link
Contributor

@veripoolbot veripoolbot commented Dec 13, 2018

Author Name: Aleksander Osman
Original Redmine Issue: 1376 from https://www.veripool.org

Original Assignee: Wilson Snyder (@wsnyder)

The bit string created by the VerilatedFst::array2Str() method is incorrect.
The two for() loops should be swapped.
@veripoolbot
Copy link
Contributor Author

@veripoolbot veripoolbot commented Dec 19, 2018

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2018-12-19T01:53:15Z

Thanks for the report and pointing out the fix.

Fixed in git towards 4.010.
@veripoolbot
Copy link
Contributor Author

@veripoolbot veripoolbot commented Jan 28, 2019

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-01-28T12:32:17Z

In 4.010.
@veripoolbot veripoolbot closed this Jan 28, 2019
@veripoolbot veripoolbot added area: wrong runtime result resolution: fixed labels Dec 22, 2019
@veripoolbot veripoolbot assigned wsnyder Dec 22, 2019
@wsnyder wsnyder mentioned this issue May 3, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wsnyder wsnyder

Labels
area: wrong runtime result resolution: fixed
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@wsnyder @veripoolbot