[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proposal for upcoming meeting


Hi Meirav,

Thanks for the comments. Indeed the API to the language (not
the hookup to another language, but the reflective facility)
warrants it's own task force, I think. Any other opinions?

As for synthesis - it may be best to push out this subject
for a while. We should capture this as an issue and address
it when things are further along. At that time it should
probably become a TF by it's own right.

The reason for pushing out synthesis is that there is still
much progress on that front. In a year or so we will have
a firmer grip on the subject.

Cheers,

-- yaron


On Monday, October 20, 2003, at 10:42 AM, Meirav Nitzan wrote:

Hi Yaron,

1. What about the subject of API such as vpi, hvpi, Reflective Facility
etc. for the purpose of navigating the verification environment data
base?

2. what about the issue of synthesizable vs. non synthesizable language
features? would each group be responsible for determining the
synthesizable constructs within its charter?

cheers,
Meirav


Yaron Kashai wrote:

Hi there,

Here is my summary of the sporadic discussions we had so far. I would
like
to present it to the WG at the next meeting (next Monday). Please send
out any comments ASAP - it would be great if we could present this
as our consensus.

Once presented, I will start looking for volunteers to lead each task
force. I assume this group will remain as the WPTF, but it would be
best if someone other than myself will lead this - any takers?

Thanks a lot,

-- yaron

Proposed Task Forces

we recommend that the WG will charter the following task forces to
develop areas of the specification. All TF work will be viewed as
recommendation to the WG, which will be the forum approving all
such work.

1. Work plan task force (WP_TF)

Review issues submitted by WG members, recommend further action and
assign them to the appropriate task force. (An issue tracking system
will be added to the WG web site - under construction).

The WPTF may recommend that new task forces are created to deal with
issues that can not be reasonably addressed within one of the existing
task forces.

2. Basic language task force (BL_TF)

Specify the syntax and the semantics of fundamental language constructs
including syntactic macros, types, identifiers, modules, units, structs,
struct members and actions. Not including features covered by other
task forces.

3. AOP task force (AOP_TF)

Specify object oriented and aspect oriented features of the language
in particular (like and when) inheritance, extension, packages, as
well as the import statement.

4. Constraints and generation (TG_TF)

Specify the syntax and semantics of constraints and related actions,
including elaboration.

5. Coverage task force (COV_TF)

Specify the syntax and semantics of coverage features. Define the
expected behavior of the coverage database and its API.

6. Temporal expressions (TE_TF)

Specify the temporal language and its anchoring in language expressions
and actions.

This task force should also look at extensions to the temporal language
in particular the addition of a PSL flavor.

7. TCMs and concurrent semantics (TCM_TF)

Specify the concurrent behavior of e time consuming methods, including
scheduling semantics. The work shall cover "wait", "sync" and "emit"
actions,
"all-of" and "first-of" concurrent actions and e-to-e ports. The work
of this
task force should set the context for the temporal expressions task
force.

8. Foreign (HDL) access and interfaces

Specify the interaction between e and other languages (Verilog, VHDL,
System C). Specify the behavior of the language as a stand alone
environment,
a master and a slave. Define the semantics of external ports.

9. e libraries

Specify the API and semantics of all library functions defined for e.