Difference between revisions of "Compile-time/run-time flags"
From Verific Design Automation FAQ
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 | + | Note that most, but not all, compile-time flags have run-time equivalent. |
Revision as of 21:59, 1 August 2022
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.
The compile-time flags are set at compile time. They are in these files:
database/DBCompileFlags.h hdl_file_sort/HdlFileSortCompileFlags.h synlib/SynlibCompileFlags.h verilog_nl/VeriNetlistCompileFlags.h verilog/VeriCompileFlags.h vhdl/VhdlCompileFlags.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:
database/DBRuntimeFlags.h edif/EdifRuntimeFlags.h hier_tree/HierRuntimeFlags.h synlib/SynlibRuntimeFlags.h upf/UpfRuntimeFlags.h util/RuntimeFlags.h verilog_nl/VeriNetlistRuntimeFlags.h verilog/VeriRuntimeFlags.h vhdl/VhdlRuntimeFlags.h
(Depending on your Verific product configuration, you may not have all the files).
Note that most, but not all, compile-time flags have run-time equivalent.