Attendees:
Mark Hahn, Cadence (Chair)
Bob Dilly, IBM
Steve Grout, Sematech
Greg Schulte, Cadence
New action items:
Who When What
---------- ------ --------
1. Mark, Greg 3/30 Resolve whether to include tags in the
taxonomy
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
-> 3/23
2. Greg 2/16 Provide a list of PVT-dependant commands from
-> 3/2 BuildGates.
-> 3/23
3. Mark 3/2 Add operating conditions to the taxonomy
-> 3/23
4. Mark 3/2 Look into a working group meeting at DAC
-> 3/23
Closed action items:
Who When What
---------- ------ --------
1. Tom 3/10 Look into providing an internal Mentor
document on describing name spaces
Next Meeting:
The next meeting will be teleconference on Tuesday, 3/23/99
from 9-11 am PDT.
Details:
1. Review action items
Jim was planning to check with IBM's legal department on
3/10 for the Einstimer educational material.
Greg suggested that it would be useful to extend the general
syntax of DCDL to include a capability similar to the Unix
"find -exec cmd {}", which applies cmd to each of the matching
files. In DCDL, cmd would be a basic constraint setting
command. The advantage of this syntax is that it avoids the
inefficiencies of building, then parsing a long list of design
object names. The disadvantage is that it goes against the
philosophy we've previously established, that "find" and other
macros should not be part of DCDL.
Suggestion: include a section in supporting documentation for
the standard that describes various aspects of integrating
DCDL into a TCL-based application, including this approach.
2. Review progress with respect to the schedule
We went through the schedule for the joint working group
as well as for DC-WG itself. The joint working group is
basically on track, but DC-WG is significantly behind.
3. Discuss and plan remaining work
We agreed that it was unlikely that the full DCDL spec
could be completed in time for DAC demos. However, we
discussed an alternate approach where we would define
a subset of DCDL that illustrates the basic ideas for
what the DCDL syntax will look like, how it interacts
with application-specific scripting capabilities, and
how it can be used for interchange purposes.
We agreed that this approach makes a lot of sense, and
Mark and Greg completed an initial definition of the
subset after the meeting.
4. Get preliminary input on DAC'99 participation
Mark and Greg are interested in driving Cadence participation,
but need to investigate whether it is feasible to include this
given the other demos that are planned.
Bob Dilly thought that it might be possible to demonstrate
a translator to/from the Einstimer command language, extending
an existing TCL interpreter.
Steve suggested that we should be able to demonstrate these in the
EDAC "conglomerate" booth, which will include participation from
a variety of standards organizations.
We agreed that it would be interesting to build on the DAC'98
OLA demo as a test case.
5. Review parasitics boundary conditions
We didn't get to this due to schedule conflicts.
-- Mark Hahn phone: (408) 428-5399 Architect, Deep Submicron Business Unit fax: (408) 428-5959 Cadence Design Systems email: mhahn@cadence.com