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

$stime() #19

Closed
veripoolbot opened this issue Jul 5, 2008 · 5 comments
Closed

$stime() #19

veripoolbot opened this issue Jul 5, 2008 · 5 comments
Assignees
Labels
resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800

Comments

@veripoolbot
Copy link
Contributor


Author Name: Holger Wächtler
Original Redmine Issue: 19 from https://www.veripool.org
Original Date: 2008-07-05
Original Assignee: Wilson Snyder (@wsnyder)


report simulation time as 32bit integer

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2008-07-14T13:41:05Z


I had assumed $stime is really a backward compatibility thing that code shouldn't be using any more.

Can you give me an example where $stime is really needed and $time isn't more proper?

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Holger Wächtler
Original Date: 2008-07-14T14:18:18Z


isn't a implementation for backward compability trivial (just casting to 32-biti in C/C++)? In verilog testcases either the testcases have to be modified (by using $time() and then selecting the lower 32 bits), or the reference patterns, so doing this on the C++ side sounds easier, especially since it makes verilator more standard-conformant..

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2008-07-14T15:23:18Z


Yes, it's easy. I find it's often good to ask "why" as the language has lots of "easy stuff" that isn't really needed, and if it IS needed I might learn something by asking. So why?

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Holger Wächtler
Original Date: 2008-07-14T15:34:21Z


... if a language has a feature, someone will
use it, copy'n'paste code will re-use it, it will spread. Some day you
reach a point where it is easier to support it than to change the code
you have...

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2008-07-14T17:18:05Z


I'm generally of the force-people-to-update-code mindset, but given it's just a few lines.

Fixed in the HEAD.

@veripoolbot veripoolbot added resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800 labels Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: fixed Closed; fixed type: feature-IEEE Request to add new feature, described in IEEE 1800
Projects
None yet
Development

No branches or pull requests

2 participants