Compile-time/run-time flags - Revision history

Vince at 03:31, 3 March 2023

2023-03-03T03:31:58Z

Vince at 03:19, 3 March 2023

2023-03-03T03:19:09Z

Vince at 03:11, 3 March 2023

2023-03-03T03:11:49Z

Vince at 03:05, 3 March 2023

2023-03-03T03:05:28Z

Hoa at 05:59, 2 August 2022

2022-08-02T05:59:29Z

Hoa at 05:52, 2 August 2022

2022-08-02T05:52:20Z

Hoa at 01:33, 24 February 2021

2021-02-24T01:33:04Z

Hoa at 19:39, 29 November 2016

2016-11-29T19:39:51Z

Hoa at 22:46, 27 July 2016

2016-07-27T22:46:52Z

Hoa at 22:40, 27 July 2016

2016-07-27T22:40:07Z

@@ Line 1: / Line 1: @@
 '''Q: Are there options to control Verific software's behavior?'''
-There are compile-time flags and run-time flags to control Verific software's behavior.
+There are compile-time flags and run-time flags ([https://www.verific.com/faq/index.php?title=Compile-time/run-time_flags Verific Runtime Flags]) to control Verific software's behavior.
 When compile-time flags are changed, it will be necessary to rebuild the software for the flags to take effect. These flags reside in the following files:

@@ Line 36: / Line 36: @@
   </nowiki>
-Below are some examples on how to call these APIs:
+Below are examples on how to call these APIs:
   <nowiki>
      RuntimeFlags::SetVar("veri_preserve_comments", 1) ;                         // enable flag 'veri_preserve_comments'
@@ Line 50: / Line 50: @@
   </nowiki>
-Below are some examples on how to call these commands:
+Below are examples on how to call these commands:
   <nowiki>
      set_runtime_flag "db_array_naming_style" "%s\[%d\]"
      get_runtime_flag "veri_preserve_comments"
   </nowiki>

@@ Line 43: / Line 43: @@
      RuntimeFlags::GetStringVar("db_array_naming_style") ;                       // retrieve the value of 'db_array_naming_style'
   </nowiki>
 For Tcl scripting, use the following commands to control the run-time flags:

@@ Line 3: / Line 3: @@
 There are compile-time flags and run-time flags to control Verific software's behavior.
-The compile-time flags are set at compile time. They are in these files:
+When compile-time flags are changed, it will be necessary to rebuild the software for the flags to take effect. These flags reside in the following files:
- database/DBCompileFlags.h
+   database/DBCompileFlags.h
- hdl_file_sort/HdlFileSortCompileFlags.h
+   hdl_file_sort/HdlFileSortCompileFlags.h
- synlib/SynlibCompileFlags.h
+   synlib/SynlibCompileFlags.h
- verilog_nl/VeriNetlistCompileFlags.h
+   util/VerificSystem.h
- verilog/VeriCompileFlags.h
+   verilog_nl/VeriNetlistCompileFlags.h
- vhdl/VhdlCompileFlags.h
+   verilog/VeriCompileFlags.h
-The run-time flags are set at run time with the C++ API 'RuntimeFlags::SetVar()' or the TCL command 'set_runtime_flag'. They are in these files:
+If the behavior of the software needs to be changed dynamically, this can be accomplished using run-time flags. With run-time flags, toggling of behavior can occur at any time without requiring re-compilation of the software. In most cases setting a flag to '1' will enable it and setting to '0' will disable it, although there are some flags that may take on other values, such as 'veri_loop_limit' = 10000, and 'db_record_naming_style' = "%s.%s". Run-time flags reside in the following files:
- database/DBRuntimeFlags.h
+   database/DBRuntimeFlags.h
- edif/EdifRuntimeFlags.h
+   edif/EdifRuntimeFlags.h
- hier_tree/HierRuntimeFlags.h
+   hier_tree/HierRuntimeFlags.h
- synlib/SynlibRuntimeFlags.h
+   pct/PCTRuntimeFlags.h
- upf/UpfRuntimeFlags.h
+   synlib/SynlibRuntimeFlags.h
- util/RuntimeFlags.h
+   upf/UpfRuntimeFlags.h
- verilog_nl/VeriNetlistRuntimeFlags.h
+   util/RuntimeFlags.cpp
- verilog/VeriRuntimeFlags.h
+   verilog_nl/VeriNetlistRuntimeFlags.h
- vhdl/VhdlRuntimeFlags.h
+   verilog/VeriRuntimeFlags.h
-(Depending on your Verific product configuration, you may not have all the files).
+Note that depending on your Verific product configuration, you may or may not have all the files listed above. Also, most of the compile-time flags have an equivalent run-time flag to facilitate toggling of the desired behavior. For a full list of Verific's run-time flags with descriptions of their functionality, please refer to this page: [https://www.verific.com/docs/index.php?title=RuntimeFlags Verific Runtime Flags]
-Note that most, but not all, compile-time flags have run-time equivalent.
+For C++, use the following APIs to control the run-time flags:

← Older revision		Revision as of 05:59, 2 August 2022
Line 26:		Line 26:
	(Depending on your Verific product configuration, you may not have all the files).		(Depending on your Verific product configuration, you may not have all the files).

−	Note that ~~many~~, but not all, compile-time flags have run-time equivalent.	+	Note that most, but not all, compile-time flags have run-time equivalent.

← Older revision		Revision as of 19:39, 29 November 2016
Line 22:		Line 22:
	(Depending on your Verific product configuration, you may not have all the files).		(Depending on your Verific product configuration, you may not have all the files).

−	Note that many compile-time flags have run-time equivalent.	+	Note that many, but not all, compile-time flags have run-time equivalent.

@@ Line 20: / Line 20: @@
   vhdl/VhdlRuntimeFlags.h
-(Depending on your Verific product configuration, you may not have all those files).
+(Depending on your Verific product configuration, you may not have all the files).
 Note that many compile-time flags have run-time equivalent.