i'm running an rtl2gate verification and i'm running into abort point issues. the gate level netlist has scan and clock gating inserted. i'm running version 05.10-s200i have the "set flatten model -gated_clock" switch set. i've tried running a "compare effort high" run after the medium run.i've tried "set compare option -part flow" (undocumented) with "compare effort low"i've run out of ideas, and i can't find any documentation anywhere on how to deal with abort points. the cone of logic doesn't seem to complicated: there are 3 DFFs and 1 PI feeding this cone.
i was able to verify the same design using synopsys formality.
Can you try 'analyze abort -verbose' and then 'analyze abort -compare' in release 6.1? (without -part flow)Chrystian RoyConformal CoreComp AE
chrystian,your suggestion resolved all the abort points i had. can i assume that it's not neccessary to run the "analzye abort -verbose" before the compare step? thanks for your help,crack
HiCorrect. No need for 'analyze abort -verbose' if 'analyze abort -compare' did the trick.We're getting very good success with that command in 6.1.Chrystian