( ESNUG 377 Item 16 ) ------------------------------------------- [09/19/01]

From: Peter Kamphuis <peter.kamphuis@infineon.com>
Subject: An Undocumented -log_changes Option To DC's change_names Command

Hi, John,

By chance I came across SolvNet article Methodology-165, describing about
Design Compiler's change_names command and Formality.  The example in the
article uses the -log_changes option of change_names.  This option is not
documented and offers a very nice way of cumulatively logging the changes
of multiple change_names commands.  (That means you'll end up with a list
of name changes between the design before the first and after the last
change_names command.)

This log file is not only valuable input to Formality, but also to other
formal verification tools.  Use something similar to the following (in
Tcl).  Note that you must delete the log file first, in case it already
exists.

  file delete -force name_changes.log
  change_names -rules my_rules_1 -log_changes name_changes.log
  change_names -rules my_rules_2 -log_changes name_changes.log

I checked with Synopsys, this option can be used without danger.  It will
be documented in a future version.

    - Peter Kamphuis
      Infineon Technologies AG                   Munich, Germany


 Sign up for the DeepChip newsletter.
Email
 Read what EDA tool users really think.


Feedback About Wiretaps ESNUGs SIGN UP! Downloads Trip Reports Advertise

"Relax. This is a discussion. Anything said here is just one engineer's opinion. Email in your dissenting letter and it'll be published, too."
This Web Site Is Modified Every 2-3 Days
Copyright 1991-2024 John Cooley.  All Rights Reserved.
| Contact John Cooley | Webmaster | Legal | Feedback Form |

   !!!     "It's not a BUG,
  /o o\  /  it's a FEATURE!"
 (  >  )
  \ - / 
  _] [_     (jcooley 1991)