• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. HOWTO: Proving a single property with parallel engines ...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 64
  • Views 12673
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HOWTO: Proving a single property with parallel engines runs

archive
archive over 17 years ago

Single-Property, Multi-Engine Distribution
IFV now supports running multiple engines in parallel to prove assertions.  You can take advantage of multi-core/multi-CPU machines to maximize performance and reduce proof runtimes.  There is no need to experiment with engines and no need for multiple IFV runs with different engines.  You now can run all available engines in parallel. 

You can enable this capability by simply supplying a list of engines to the define engine command.  Three engines (sword, axe and bow) are now supported in distribution.  More engines will become available in subsequent IFV releases.

Example settings:

# Select 3 engines to run in parallel
define engine sword axe bow

# Select 2 engines to run in parallel
define engine sword axe

Note the following regarding distribution:

    • If more engines than available cpus are specified on a resource, IFV will generate an error and ignore the engine setting.  Users can override this by the cpu_sharing on  setting:

      # Enable more engines to run than available cpus on a machine
      define cpu_sharing on
    • When submitting jobs via LSF, remember to reserve appropriate number of cpus for the job.  Please consult your IT professional on specific instructions for requesting appropriate number of free cpus to run IFV on a single machine. 

      In general you need to specify the –n option (requests specified free cpu resources) to bsub and specify span[hosts=1] (keeps the cpu reservation on the same machine) in the resource specification (-R argument).
    • At this time no_deadlock FSM checks are not supported in distribution.  You will need to define a single engine if you chose to run no_deadlock FSM checks.


Originally posted in cdnusers.org by jb
  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information