Re: SCE-MI 2.0 Issues

Greetings ITC Techies,

Duaine and I also had an action from last meeting to send
a list of issues that need committee discussion.

I'll list what I have here. Some of these are the same as
items in Per's list that he just sent out.

- What common subset of DPI function arg data types will
   SCE-MI 2 support that can cleanly span Verilog, SystemVerilog,
   VHDL as per the requirements ?

- Data shaping for pipes - bit or byte resolution ?

- Is current comment based pragma syntax attributing scheme adequte
   for Verliog, VHDL ?
   - Specifically for VHDL should we explore using attributes
     instead ?

- What degrees of recursion can you call imports from exports,
   exports from imports, etc ?
   - Lets keep it limited at first
   - We propose Russ's proposal as a starting point

- Time, cycle stamp handling in SCE-MI 2

- Exported task support

- Use of DPI 'context' keyword for imported functions
   - Require it for SCE-MI 2 ? (Matt raised this)

- Issues surrounding macro semantics and compatibility
   with function semantics and guaranteed determinism
   for streaming


-- johnS




Per Bojsen wrote:
> Hi,
> 
> at the last meeting we agreed that we would start to collect issues
> that need to be discussed as a part of the process of fleshing out
> the Mentor proposal and turning it into a standard.  I have not seen
> anyone else sending anything out, but here is my list:
> 
>   1) Firming up what we are going to do for Verilog and VHDL both
>      relative to the Mentor proposal and Cadence's proposal for
>      new macros.
> 
>   2) The list of data types supported in DPI calls.
> 
>   3) Whether there should be any restrictions on DPI functions calling
>      each other.
> 
>   4) SceMiClockPort in DPI-only applications.
> 
>   5) SceMi::Init(), SceMi::Version(), SceMi::Shutdown() in DPI-only
>      applications.
> 
>   6) SceMiParameters: is this required in DPI-only applications?
>      Do we need new attributes for DPI?
> 
>   7) Firming up the seams between the new DPI-based features and
>      the SCE-MI 1.1 features: restrictions on mixing etc.
> 
>   8) Deciding whether simulator support is required for a compliant
>      implementation.
> 
> There is much more, I'm sure, but this is a start.
> 
> Thanks,
> Per
> 
> --
> Per Bojsen                                Email: <bojsen@zaiqtech.com>
> Zaiq Technologies, Inc.                   WWW:   http://www.zaiqtech.com
> 78 Dragon Ct.                             Tel:   781 721 8229
> Woburn, MA 01801                          Fax:   781 932 7488
> 
> 

-- 

This email may contain material that is confidential, privileged
and/or attorney work product for the sole use of the intended
recipient.  Any review, reliance or distribution by others or
forwarding without express permission        /\
is strictly prohibited. If you are     /\   |  \
not the intended recipient please     |  \ /   |
contact the sender and delete        /    \     \
all copies.                      /\_/  K2  \_    \_
______________________________/\/            \     \
John Stickley                   \             \     \
Mgr., Acceleration Methodologies \             \________________
Mentor Graphics - MED             \_
17 E. Cedar Place                   \   john_stickley@mentor.com
Ramsey, NJ  07446                    \     Phone: (201) 818-2585
________________________________________________________________