Attendees:
Mark Hahn, Cadence (Chair)
Tom Dewey, Mentor Graphics
Bob Dilly, IBM
Steve Grout, Sematech
New action items:
Who When What
---------- ------ --------
1. Tom 3/10 Look into providing an internal Mentor
document on describing name spaces
Open action items:
Who When What
---------- ------ --------
1. Jim 1/19 Investigate whether IBM could provide the
-> 2/16 Einstimer educational material as a reference
-> 3/2
2. Greg 2/16 Provide a list of PVT-dependant commands from
-> 3/2 BuildGates.
3. Mark 3/2 Add operating conditions to the taxonomy
4. Mark 3/2 Look into a working group meeting at DAC
Closed action items:
Who When What
---------- ------ --------
1. Mark 3/2 Investigate namespace issues (escaping,
case sensitivity, delimiter characters)
Next Meeting:
The next meeting will be a face to face meeting at Cadence's
Seely Ave campus in Building 7, the Sausalito conference room
with a simultaneous teleconference on Wednesday, 3/10/99,
from 9-12 am PDT.
Details:
1. Review action items
Mark completed a first pass at the name space issues.
No progress yet on other action items.
2. Discuss name space issues
We discussed this but didn't reach any firm conclusions.
In general, there was a desire to provide both high level,
easy to understand and use commands, such as
dcd::name_space -verilog
as well as lower level controls for flow developers and
expert users, which would set specific aspects of the
name space such as the hierarchy delimiter, bus delimiters,
and case sensitivity.
It was noted that the Verilog LRM does specify that "."
is to be used as the hierarchy delimiter.
3. Discuss naming convention for commands:
- set_xyz versus xyz
- unset_xyz versus remove_xyz versus nothing
We tentatively agreed to
a. dcd::<constraint_name> parameters ...
b. dcd::<constraint_name> -remove parameters ...
c. dcd::<constraint_name> -merge parameters ...
as the convention for how to specify <constraint_name>,
remove a previously specified constraint or part of its effect,
and merge the values specified in a new constraint with the
previously specified values in a worst-case fashion.
4. Review parasitics boundary conditions
Steve Grout wasn't able to attend the full meeting, so we
deferred this to the face to face meeting.