Skip to content
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

incorrect handling of strings in display and sformatf #1441

Closed
veripoolbot opened this issue May 15, 2019 · 3 comments
Closed

incorrect handling of strings in display and sformatf #1441

veripoolbot opened this issue May 15, 2019 · 3 comments
Assignees
Labels
area: wrong runtime result Issue involves an incorrect runtine result from Verilated model resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor


Author Name: Denis Rystsov
Original Redmine Issue: 1441 from https://www.veripool.org

Original Assignee: Wilson Snyder (@wsnyder)


$display of a string parameter or an expression with type string produces incorrect result in certain cases.
Please see the attached test case cases 2 and 4.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-05-16T01:58:57Z


Thanks for putting this in test_regress format, that helps.

First bug is at present it assumes %h when no display format provided. Second bug is loss of string when constant propagated in parameter; note however some other simulators don't allow $sformatf in constant functions (Verilator intended to support it however).

Will look at a fix this weekend.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-05-17T01:22:45Z


Both issues fixed in git towards 4.015.

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-06-16T13:58:51Z


In 4.016.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: wrong runtime result Issue involves an incorrect runtine result from Verilated model resolution: fixed Closed; fixed
Projects
None yet
Development

No branches or pull requests

2 participants