Re: [sv-bc] @* vs. always_comb

From: Steven Sharp <sharp_at_.....>
Date: Tue Dec 13 2005 - 18:36:26 PST
>From: "Brad Pierce" <Brad.Pierce@synopsys.com>

>Synthesis already handles hierarchical references just fine, including
>hierarchical function calls, as long as the references are into
>interface instances.

Does this apply to generic interfaces, or only ones where you have
seen the declaration of the interface?  The problems become a lot
easier if you get to see the interface declarations first.  References
to functions imported from packages don't cause problems for that reason.

The term "hierarchical reference" may be too broad here.  Some cases
are more problematic than others.  A select of a member of a local
struct could be considered a hierarchical reference down into the
hierarchy of the struct, but clearly doesn't create the problems that
we are discussing.

The problems that Gord mentioned with hierarchical function calls in
always_comb blocks may not occur with hierarchical references into
non-generic interfaces.  I don't know.


Steven Sharp
sharp@cadence.com
Received on Tue Dec 13 18:36:30 2005

This archive was generated by hypermail 2.1.8 : Tue Dec 13 2005 - 18:36:59 PST