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 . RegardsJentil Jose
Hi Jentil Jose.If you have more than one licence available, you could use a TCL script to control the proof, such that only N properties are proven in each run. Then run IFV on multiple machines, with a parameter to the TCL file which selects the set of properties to prove on that machine.If your assertions have a good naming scheme it would be easy to use the "assertion -delete" command to select the properties by IP block name for example.Of course you'd need to merge the results after all the runs complete, but that would be fairly easy with a bit of perl or awk scripting.
Hi Steve H . Thanks , This sounds helpful for me . However , is there a way to run different IFV sessions in a single run directory ? I suppose a lock file is generated to avoid multiple sessions in a single run directory .RegardsJentil Jose
Good point!I would imagine that you could use the +nclibdirname+
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
Hi Jose , I used IFV 6.11s001 in non GUI , this solves my problem . Thanks for the suggestion. RegardsJentil