DC-WG: 3/21 meeting minutes


Subject: DC-WG: 3/21 meeting minutes
From: Mark Hahn (mhahn@cadence.com)
Date: Tue Apr 04 2000 - 07:46:05 PDT


Meeting minutes from the 3/21/00 DC-WG teleconference
-----------------------------------------------------

Attendees:
  Mark Hahn, Cadence
  Tom Dewey, Mentor
  Bob Dilly, IBM
  Jim Engel, ITM
  Vassilios Gerousis, Infineon
  John Paul, IBM

New action items:

      Who When What
      ---------- ------ --------
 1. Tom 3/28 Update the spec with changes
 2. Bob 3/28 Create a block diagram that shows the
                           relationship between the TCL interpreter,
                           DCDL TCL cmds, and the reference parser

Closed action items:

      Who When What
      ---------- ------ --------
 1. Tom 3/21 Update the spec with changes

Next Meeting:

  The next meeting will be a teleconference on 3/28/00
  from 10-12 am (PDT)

Details:
  1. Reference parser

     Bob is working on the legal issues within IBM to make the
     reference parser available through an open source license
     agreement. The first step is for IBM to join OVI.

     Mentor has done the first integration of the preliminary
     version of the parser into a tool. The schedule for adding
     support for the full set of commands into the parser is
     being worked on. IBM plans to separate the parser from the
     "database" of in-memory constraints.

     The parser today is implemented to support pure DCDL, and
     it needs additional work to fit within a TCL scripting environment.

  2. DAC planning

     Booth space is available. It's not clear what other groups
     will be showing in the booth.

     Tom will look into whether it's possible to demo a Mentor
     front-end tool, with more presentation than interaction.

     Tom played with the PicoJava core. Some of the blocks in
     the design are full custom and are modeled as black boxes;
     if we were to use the design we would need the contents of
     the blocks.

  2. Discuss modes

     We agreed to add the functional_mode command, as there is
     little controversy on this. We need to decide on the
     default behavior when there are multiple modes and mode
     groups (are all modes active, or is there a default mode
     defined in the library for each component?). OLA follows
     the latter approach.

  3. Start discussion on scoping commands

     We agreed to consolidate current_instance and current_module
     into a current_scope command with -instance and -cell options.
     To navigate to the top level cell in the design, the -top
     option can be used, and moving up one or more levels relative
     to the current scope can be done with the -up # option.

     There were some unresolved issues with relative path names.

Thanks,
Mark

-- 
Mark Hahn                                          phone: (408) 428-5399
Senior Architect                                   fax:   (408) 428-5959
Cadence Design Systems                             email: mhahn@cadence.com



This archive was generated by hypermail 2b28 : Tue Apr 04 2000 - 07:50:19 PDT