[logo] 
Home
News
Activity
About/Contact
 Major Tools
 .. BugVise
 .. Dinotrace
 .. Verilator
 .. Verilog-mode
 .. Verilog-Perl
 .. Vregs
 Other Tools
 .. Gspice
 .. IPC::Locker
 .. Schedule::Load
 .. SVN::S4
 .. Synopsys-modes
 .. SystemPerl
 .. Verilog-Pli
 .. Voneline
 General Info
 .. Book Tips
 .. Papers

Issue #19

$stime()

Added by Holger Wächtler 54 days ago. Updated 45 days ago.

Status :Closed Start :07/05/2008
Priority :Normal Due date :
Assigned to :Wilson Snyder % Done :

0%

Category :Unsupported
Target version :-

Description

report simulation time as 32bit integer

History

07/14/2008 01:41 PM - Wilson Snyder

  • Status changed from New to AskedReporter
  • Assigned to set to Wilson Snyder

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?

07/14/2008 02:18 PM - Holger Wächtler

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..

07/14/2008 03:23 PM - Wilson Snyder

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?

07/14/2008 03:34 PM - Holger Wächtler

... 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...

07/14/2008 05:18 PM - Wilson Snyder

  • Category set to Unsupported
  • Status changed from AskedReporter to Closed

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

Fixed in the HEAD.

Also available in: Atom PDF