Re: Connect-ResolveTo stmt proposal (resend with changes)


Subject: Re: Connect-ResolveTo stmt proposal (resend with changes)
From: Kevin Cameron (Kevin.Cameron@nsc.com)
Date: Tue Apr 16 2002 - 10:17:46 PDT


I would like to suggest that warnings are issued only for mismatching attributes
when there are multiple possible results, and only for attributes that are
relevent to the tool being used. E.g. if you calculate 'a' & 'b' are possible
resolution results and they have the same simulation tolerance attributes, no
warning would be issued by a Verilog-AMS simulator.

Vendors can added command-line switches for other modes.

Kev.

Srikanth Chandrasekaran wrote:

> Problem:
> --------
> With the current version of the LRM there is lot of ambiguity with regards to
> which of the rules apply when trying to do discipline resolution
>
> connect x y b resolveTo b
> connect x y resolveTo x
> connect x y a resolveTo a
>
> In the above set of rules it is not clear, when two nets having disciplines x
> & y will be resolved to b, z, or a.
>
> Also it is not clear in the LRM whether the resolved discipline should be part
> of the list specified.
>
> Proposal:
> ---------
> When there is an exact match for the set of disciplines specified, the
> resolved discipline would be as per the rule specified in the exact match.
> When more than one specified rule applies to a given scenario a "Warning"
> message shall be issued by the simulator and the first match would be used.
>
> When there is no exact fit, then the resolved discipline would be based on the
> subset of the rules specified. If there is more than one subset matching a set
> of disciplines, the simulator shall give an "Warning" message and apply the
> first subset rule that satisfies the current scenario.
>
> The resolved discipline need not be one of the disciplines specified in the
> discipline list.
>
> The connect-resolveto shall not be used as a mechanism to set the disciplines
> of simulator primitives but used only for discipline resolution.
>
> Example 1:
> ----------
> connect x y a resolveTo a
> connect x y resolveTo x
>
> x,y would resolve to x.
> x,y,a would resolve to a
> y,a would resolve to a
>
> Example 2:
> ----------
> connect x y a resolveto a
> connect x y resolveTo x
> connect x y b resolveto z
>
> x,y would resolve to x
> x,y,b would resolve to z
> y,a would resolve to a
>
> Example 3:
> ----------
> connect x y a resolveto a
> connect x y b resolveto b
>
> x,y would resolve to a with "Warning"
> y,a would resolve to a
> y,b would resolve to b
>
> Example 4:
> ----------
> connect x y resolve to x
> connect x y resolve to y
>
> x,y would resolve to x with "Warning"
>
> --
> Srikanth Chandrasekaran
> Global Software Group, EDA SBU
> Motorola Australia.
> Phone: +61-8-8168 3592 Fax: x3501



This archive was generated by hypermail 2b28 : Tue Apr 16 2002 - 10:20:48 PDT