User`s manual

Simulation
ModelSim Xilinx User’s Manual Verilog Simulation 5-69
+no_pulse_msg
This option disables the warning message for specify path pulse errors. A path
pulse error occurs when a pulse propagated through a path delay falls between the
pulse rejection limit and pulse error limits set with the +pulse_r and +pulse_e
options. A path pulse error results in a warning message, and the pulse is
propagated as an X. The +no_pulse_msg option disables the warning message,
but the X is still propagated.
+no_tchk_msg
This option disables error messages issued by timing check system tasks when
timing check violations occur. However, notifier registers are still toggled any
may result in the propagation of X’s for timing check violations.
+nosdfwarn
This option disables warning messages during SDF annotation.
+notimingchecks
This option completely disables all timing check system tasks.
+nowarn<mnemonic>
This option disables the class of warning messages specified by <mnemonic>.
This option only disables warning messages accompanied by a mnemonic
enclosed in square brackets. For example,
# WARNING: test.v(2): [TFMPC] - Too few port connections.
This warning message can be disabled with the +nowarnTFMPC option.
+pulse_e/<percent>
This option controls how pulses are propagated through specify path delays,
where <percent> is a number between 0 and 100 that specifies the error limit as a
percentage of the path delay. A pulse greater than or equal to the error limit
propagates to the output in transport mode (transport mode allows multiple
pending transitions on an output). A pulse less than the error limit and greater than
or equal to the rejection limit (see +pulse_r
(5-70)) propagates to the output as an
X. If the rejection limit is not specified, then it defaults to the error limit. For
example, consider a path delay of 10 along with a +pulse_e/80 option. The error
limit is 80% of 10 and the rejection limit defaults to 80% of 10. This results in the
propagation of pulses greater than or equal to 8, while all other pulses are filtered.
Note that you can forcespecify path delays to operate in transport mode by using
the +pulse_e/0 option.