( ESNUG 258 Item 1 ) -------------------------------------------- [2/7/96]
Subject: ( ESNUG 257 #6 ) Bad DC! -- Getting DC To Clean Up After Itself
> I use parameterized templates extensively in my Verilog designs. When
> Synopsys reads in these templates, it creates a few temporary files with
> names like "*.mra", and "*verilog.syn". Problem is, messy Synopsys
> doesn't clean up these files upon exit. My directories are really
> starting to get cluttered! Do any of your readers have any tricks to get
> Synopsys to not create these files, or redirect them to a junk directory?
From: pbarrett@su102s.ess.harris.com (Phil Barrett)
John,
Regarding the problem with synopsys writing cache files to your synopsys
directory and cluttering it up, I may not fully understand your problem,
but there may be a simple solution. Create a work directory in your
synopsys directory. Add the following to your .synopsys_dc.setup file:
define_design_lib work -path ./work
cache_read = cache_read + {./work}
cache_write = "./work"
This should write all of your *.mra, *.sym, etc. files to the work directory
you created. I am not familiar with the use of parameterized templates,
or for that matter Verilog design, but any synthesis related files should
write to the work directory with these additions.
- Phil Barrett
Harris Corp., Palm Bay, FL
---- ---- ---- ---- ---- ----
From: ajoy@rendition.com (Ajoy Aswadhati)
Hi John, To reduce the clutter in your synthesis directory....
UNIX>mkdir WORK
at the beginning of your synthesis script:
dc_shell>define_design_lib work -path ./WORK
- Ajoy Aswadhati
Rendition Inc, Mountain View, CA
---- ---- ---- ---- ---- ----
John,
Assuming these are being created in your "WORK" library (the default for
the analyze command) then use this dc_shell command:
define_design_lib WORK -path the/directory/you/want
Now the "WORK" design library is mapped into whatever directory you want.
I typically use "../work" or "~/work". Make sure the directory exists
before you use it.
- Steve Golson
Trilobyte Systems
---- ---- ---- ---- ---- ----
From: Paul Zimmer <prz@hplb.hpl.hp.com>
Hi, John.
My complaints about this to Synopsys have fallen on deaf ears. It's
worse than messy, it's destructive.
The REST of DC, and other synopsys tools (except perhaps BC), behave like
good little editors. You read something in, do whatever bizarre, deviant
things you want to them, and, as long as you don't do a write, you can
exit without having done a bit of damage.
Not so with parameterized designs. You do a simple *read*, and the thing
defecates all over the file system! VERY irritating! Why doesn't it
just create the .mra, etc stuff as objects in dc, and write them out if
and when you say so?
I agree - Bad DC! Bad DC!.
- Paul Zimmer
HP, Bristol, UK
|
|
