---------------------------------- Ian M Wilson Architect Berkeley Design Automation Office: 408-496-6600 x238 Cell: 714-272-7040 ian.wilson@berkeley-da.com http://www.berkeley-da.com ---------------------------------- True SPICE accuracy, 5X-20X faster Don't Be Left Behind! ----------------------------------Nothing to do with wreal (that is user defined nettype), my mistake.
Generic interconnect is related to how we handle pass through mechanics in Verilog-AMS.
Currently it is undocumented and undefined, but implementations piggy back on "wire".
We need to fix this in SV-AMS anyway.
The generic interconnect proposal does that work for us and should be fully compatible with Verilog-AMS when the time comes.
So no - defiantly no divergence, more a convergence by introducing a defined and documented construct to handle this issue in both languages.
Whether the old "wire" method (existing models) will be able to be used in a SV-AMS world, we really can't tell at this stage, but that is not SV's concern. That is more a backward compatibility question we have to address, and backward's compatibility is not always a good thing.
Cheers..
Dave
On 10/24/2011 11:24 AM, Little Scott-B11206 wrote:
Hi Dave:
1. Brad Pierce is a member of the Champions committee from SNPS.
2. If Verilog-AMS wants to comment on their perspective about whether this proposal creates a divergence between SV and Verilog-AMS that would likely be a good thing. My guess is that Brad is simply curious what effect the interconnect will have on the Verilog-AMS/SV merger. I would expect he doesn't want SV-DC to do something that would significantly complicate the merger. I haven't heard any concerns from SNPS, so I don't believe the question comes from anyone at SNPS other than Brad.
I read the feedback, and I was going to prepare a response in the next couple of days. I would send out that response to the SV-DC reflector to iterate on the wording a bit prior to sending it along to Brad. If Verilog-AMS would like to be included and make it a joint response to Brad that would be fine. Your thoughts?
I think that a bit of explanation about how SV-DC& Verilog-AMS are interacting would also be useful.
Thanks,
Scott
-----Original Message-----
From: Miller Dave-A17239
Sent: Monday, October 24, 2011 10:11 AM
To: Little Scott-B11206
Cc: Chandrasekaran Srikanth-A12788; ian.wilson@berkeley-da.com
Subject: Re: Fwd: [sv-dc] Results from the most recent Champions email
vote
Sorry meant to also include Ian in response.
On 10/24/2011 10:08 AM, Dave Miller wrote:
bc@eda.org>,
-------- Original Message --------
Subject: [sv-dc] Results from the most recent Champions email vote
Date: Sat, 22 Oct 2011 19:52:03 -0700
From: Neil Korpusik<neil.korpusik@oracle.com>
Reply-To:<neil.korpusik@oracle.com>
To: 'sv-ac@eda-stds.org'<sv-ac@eda-stds.org>, SV_BC List<sv-
SV_EC List<sv-ec@eda.org>,<sv-dc@eda.org>ended
The proposal was opposed by the Champions in the email vote which
October 17, 2011.about
....
3724 SV-DC Allow generic interconnect for "typeless" connections
Scott, I saw this, as well as the comment in the Mantis:
<QUOTE>
Opposed:
Brad
Before approving, I'd like to hear the official position of SV-DC
whether this is a divergence away from Verilog-AMS, and if so, whythat
divergence is considered necessary.the
</QUOTE>
1. Who is Brad?
2. Is there anything that we (Verilog-AMS) can do to help here? Is
divergence regarding wreal vs generic interconnect?closely
Is it simply a matter of pointing out that the two groups work
together, and that Verilog-AMS (Ian) is directly involved with theproposal to
ensure that the SV proposal will play nice with AMS in the future?be a
Of course any technical person must understand that there will always
little bit of give and take when two languages like this are mergedtogether.
--
==============================================
-- David Miller
-- Design Technology (Austin)
-- Freescale Semiconductor
-- Ph : 512 996-7377 Fax: x7755
==============================================
This archive was generated by hypermail 2.1.8 : Mon Oct 24 2011 - 14:51:21 PDT