( ESNUG 246 Item 3 ) ---------------------------------------------- [8/8/96]
Subject: (ESNUG 244 #7) It's DESIGN Compiler *not* Behavioral Compiler Bug!
David Black's orginal wording of ESNUG 244 #7 was:
> As to seeing any bugs... I have seen a few bugs with v3.4b-BC2 and not
> necessarily related to Behavioral Compiler. Here is one that is logged
> with Synopsys, but unresolved at the moment.
>
> Compiling a top level module that merely instantiated two lower level
> modules that were previously compiled produced a weirdness. A control net
> that is definitely functional within the design (pre-synthesis) was
> disconnected between the two modules (it's an output from one, and an
> input to the other). The dangling input was then tied HIGH!? +%#@!! :-(
From: jcooley@world.std.com (John Cooley)
As the ESNUG guy, I'm always looking for ways to condense an engineer's
post down to the core issue. Because I know David Black uses Behavioral
Compiler a lot, I just assumed he was talking about BC in his second
paragraph above. Like an idiot I dropped his first paragraph and reworded
the first sentence in his second paragraph to read:
> While compiling a top level module in Behavioral_Compiler that merely
> instantiated two lower level modules (that were previously compiled)
> produced a weirdness. A control net...
It turns out he was talking about *Design Compiler* in his second paragraph,
not *Behavioral Compiler*! Sorry, folks. My goof!
- John Cooley
the ESNUG guy
|
|
