( Post 55 Item 1 ) ------------------------------------------------------------
> From: Justin TH CHUA <chua@hpsgwj.sgp.hp.com>
> I joined the group late, and the first posting that I received is #46.
> So, I think I have missed out a lot of the discussions. Just wonder if
> I can receive the back copies from somewhere?
> From: mills@hwcae.az.honeywell.com (Don Mills)
> Would it be possible to get the back issues (postings) of
> ESNUG. Posting 40 was the first one I received. I have found the
> information from ENSUG postings to be extremely valuable. I
> wonder what additional information I might have missed in postings
> previous to posting #40.
ADMIN NOTE: The posts prior to 40 were discussions between a few
people of what ESNUG should be. Because they didn't contain any
information of techinical interest, I never bothered keeping them.
But, the posts starting at #40, I've kept and have been sending
them to people who request them. Also, I've had someone I met at the
'92 SNUG write saying he'd be interested in setting up an archive
on his system. Once we get this worked out, I will post how to access
these.
- John Cooley
( Post 55 Item 2 ) ------------------------------------------------------------
From: Dominique Dumont / GND <domi%desire.grenoble.hp.com@hplb.hpl.hp.com>
Could people tell what's the version number of Synopsys they are dealing
with ? Some problem may arise on early version while they are solved on
later ones.
( Post 55 Item 3 ) ------------------------------------------------------------
> Subject: ESNUG Posting Number 52 ( Item # 2 )
> From: Jay McDougal <jaym@hpcvcbu.cv.hp.com>
>
> Hello,
>
> I came across the following bug while trying to ungroup a hierarchical
> design that had children of children with dont_touch attributes.
>
> I was using ungroup -all -flat to remove the hierarchy but there were
> some cells in the hierarchy that I had compiled with dont_touches
> because I wanted them to use special Flip-Flops. When the design
> was flattened, the dont_touched modules were also flattened!!
>
> To get around this problem I had to call ungroup -all repeatedly
> until all the hierarchy was flat. This left the dont_touched modules
> intact!
From: hecht@shark.eng.hou.compaq.com (Stuart Hecht)
I thought of one way around that problem, although I'm not sure what problems
it would cause in your specific case. Designs that aren't read in can't be
ungrouped. So, if you have:
A --- B --- C
\--- D
If you don't read in D (or if you write it out and then do a remove_design D)
then when you do the ungroup -all -flatten, D will not be ungrouped since
Synopsys doesn't know what D contains.
Stu
|
|
