( ESNUG 387 Item 4 ) --------------------------------------------- [01/23/02]
Subject: ( ESNUG 385 #11 ) Can't Duplicate This "insert_dft -physical" Bug
> 1) insert_dft seems to spend a *long* time, fixing DRC violations. We
> are getting better runtimes and lower gatecounts with insert_scan
> followed by a 'physopt -incremental -eco'.
>
> - Neel Das
> Corrent Corp. Tempe, AZ
From: "Andrew Copper" <acopper@synopsys.com>
John,
So far we have not seen any such issues in-house or from other customers
using "insert_dft -physical" concerning long run-times to fix DRCs or
larger gate counts (as compared to using a combination of "insert_scan
-physical" and "physopt -inc -eco" commands.)
The "insert_dft -physical" command automatically performs any necessary
placement legalization and timing optimization apart from fixing
testability violations. It replaces the need to run three separate
commands of "insert_scan -physical" followed by "legalize_placement -eco"
and "physopt -incremental".
Maybe Neel could send us a test case?
- Andrew Copper
Synopsys, Inc. Mountain View, CA
|
|
