( ESNUG 468 Item 1 ) -------------------------------------------- [09/13/07]
Subject: ( ESNUG 467 #4 ) It's trivial to see DC/Formality guidance files
> This is my one and only objection to Formality's use of guidance files.
> Knowing that Formality ignores bad guidance isn't as important to me as
> knowing that DC doesn't generate bad guidance in the first place. Again,
> I don't mind the tools passing notes, as long as they're not secret notes!
>
> Is there a flag to make DC write out a "text" SVF?
>
> - Tom Mannos
> Sandia National Labs. Albuquerque, NM
From: David Smith <dave.smith=user domain=st not calm>
Hi, John,
I don't believe that there is a way to make *DC* write out a "text" SVF; at
least, when we asked our Synopsys AE, he said that there wasn't.
However, Formality writes out a text version of the SVF as it reads in the
binary version -- if your SVF file is <filename>.svf, then your text version
will be <filename>.svf.txt. Alternatively, you can use the report_guidance
command to get a text version of your SVF.
I believe you can then use this text version (potentially with your edits)
instead of the binary one in a second Formality run.
Of course, you can also use this route if you're paranoid that Formality
isn't telling you everything about what's in the SVF.
- David Smith
ST Microelectronics Bristol, UK
---- ---- ---- ---- ---- ---- ----
From: Arvin Patel <a.patel=user domain=ti not calm>
Hi, John,
The guidance information Tom is looking for can be viewed in an ASCII text
file that Formality produces during every run when the SVF file is specified
with the set_svf command. The text file has the same name as the SVF with
ending .txt. Alternatively it should be possible to view guidance info from
a previous set_svf command with the report_guidance command.
- Arvin Patel
Texas Instruments Oslo, Norway
---- ---- ---- ---- ---- ---- ----
From: John Lehman <john.lehman=user domain=synopsys not calm>
Hi, John,
The SVF file created by Design Compiler is written out in a compact form.
When you read SVF files into Formality, a single expanded and concatenated
ASCII file is automatically written out. You can examine the full content
of the ASCII SVF file and you can read the ASCII version into Formality to
confirm that it has the same effect as using the compact form of SVF.
You can also modify the ASCII version as you wish before reading it into
Formality as Silver Surfer did (see ESNUG 465 #3) to prove that Formality
validates SVF guidance before using it.
- John Lehman
Synopsys, Inc. Mountain View, CA
Index
Next->Item
|
|
