murphi2smv1
Translate a murphi model to smv
Usage
murphi2smv [{--output
FILE | -o
FILE}]
FILE
Overview
The utility murphi2smv is bundled with the model checker Rumur and can be used to translate a Murphi model into the input format to the NuSMV model checker. See rumur(1) for more information about Rumur or Murphi.
Options
-
--help or -? -
Display usage information.
--numeric-type [integer | word] or -n [integer | word]
Set the SMV type used for ranges, scalarsets and numeric literals. This can be either integer to use native integers or word to use bit-vectors. If this option is omitted, one is chosen automatically based on the content of the input model.
-
--output FILE or -o FILE -
Set the path to write the output SMV model to. If this argument is omitted, output is written to standard out.
-
--quiet or -q -
Silence warning diagnostics.
-
--verbose or -v -
Report extra debugging information.
-
--version -
Display version information and exit.
Notes
Translation to SMV is imprecise because the semantics of model execution in SMV are significantly different to Murphi. murphi2smv should not be expected to give you a ready-to-run SMV model. Rather it gives you an initial rough translation that you will need to edit to form a runnable model.
Limitations
Murphi type declarations have no exact equivalent in SMV. These are handled by propagating and expanding them inline. This is done purely syntactically, which can lead to unexpected or incorrect results if your input model has symbols that shadow other symbols.
The following Murphi constructs have no equivalent in SMV and are emitted as a placeholder comment:
•
|
|
|---|---|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
quantifiers |
•
|
|
•
|
simple |
•
|
|
•
|
|
•
|
|
•
|
|
You will need to either rephrase your input model to avoid these features or edit the generated SMV after generation.
Rumur supports integers up to 64-bit in width. SMV integers are only 32-bit. There are no checks that the numbers or calculations in the input model fit in 32-bit. This may result in constants or calculations in the generated SMV that overflow.
Murphi rule-local declarations and variables have no equivalent in SMV. These are emitted using SMV syntax but will need to be moved to a valid location within the SMV output.