Surya, I consider this to be valid code. Both "bind" and hierarchical resolution are aspects of elaboration activity. So components that are created via a bind are conceptually similar to a conditionally elaborated generate. Since "test.m1.p1.b1" doesn't bind to a select, it participates in the hierarchical resolution which must be permitted to interact with the bind. It is an implementation issue as to whether this impacts simulation performance; there are certainly approaches where this would not. Gord. Surya Pratik Saha wrote: > Hi, > I have seen some discussions are going on for binded instances. I have > one issue to be clarified. > > As per LRM, a binded instance will be inserted to a particular target > scope or instances. But LRM is not clear whether the binded instance > will be part of that target scope or instances. Basically I have got > some cases, where hierarchical reference is done though binded instance > starting from the target scope. For e.g. > > module test(); > mid m1(); > > bind mid prog1 p1(); // bind stmt > > initial > test.m1.p1.b1 = 1'b1; > endmodule > > module mid( ); > endmodule > > module prog1; > bit b1; > endmodule > > Some of the simulators are passing this type of test case. But I think, > to support this type of hierarchical reference, any scope variable > resolution involving instance needs to be stopped until all bind > construct of the whole design are resolved, which will impact on runtime > of any tool. Is it a desired behaviour? > -- -------------------------------------------------------------------- Gordon Vreugdenhil 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Jun 4 07:30:12 2007
This archive was generated by hypermail 2.1.8 : Mon Jun 04 2007 - 07:30:22 PDT