Stats

  • Locked Locked
  • Replies 8
  • Subscribers 64
  • Views 15460
  • 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

IFV Regresssion

archive

Hello ,

   I am using IFV to check the hook up in a large SOC .
   We have around 2000 assertions .  That means the total 
   assertion run takes so much time ( I am using a single IFV gui ) .

    Is there any workaround ? like simulations can we have batch mode 
    jobs for these assertion runs . We are using a farm of servers .  

Regards

Jentil Jose


Originally posted in cdnusers.org by jent
Parents

  • Jentil,

    Which version of IFV are you using?  IFV 6.11s001 provided a significant performance boost over previous versions out of the box.  Please ensure you are using s001 or newer version.

    Another thing to try is to run the proof without the GUI.  You can always bring up the gui at the end of the proof by running the tcl command "simvision" at the formalverifier prompt.  See if the runtimes are significantly improved.

    Try this before creating parallel runs. This alone may avoid you having to break up your runs.

    Regards,

    Jose


    Originally posted in cdnusers.org by jb
Reply

  • Jentil,

    Which version of IFV are you using?  IFV 6.11s001 provided a significant performance boost over previous versions out of the box.  Please ensure you are using s001 or newer version.

    Another thing to try is to run the proof without the GUI.  You can always bring up the gui at the end of the proof by running the tcl command "simvision" at the formalverifier prompt.  See if the runtimes are significantly improved.

    Try this before creating parallel runs. This alone may avoid you having to break up your runs.

    Regards,

    Jose


    Originally posted in cdnusers.org by jb
Children
No Data

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.