errata/570: errata/570: more problems

From: Steven Sharp (sharp@cadence.com)
Date: Mon Apr 12 2004 - 15:10:01 PDT

  • Next message: Steven Sharp: "Action item for generate"

    The following reply was made to PR errata/570; it has been noted by GNATS.

    From: Steven Sharp <sharp@cadence.com>
    To: etf-bugs@boyd.com
    Cc:
    Subject: errata/570: more problems
    Date: Mon, 12 Apr 2004 18:26:17 -0400 (EDT)

     The description also ignores the possibility that the module_instance_name
     could actually be a named block scope name instead. And it ignores the
     possibility that an upward search might need to traverse upward through
     named blocks and a task or function scope before reaching the module level.
     
     Example of these:
     
     module top;
     initial
     begin:foo1
       begin:foo2
         reg bar;
       end
       begin:foo3
         $display(foo2.bar);
       end
     end
     endmodule
     
     Here foo2 is not a module name, and the upward reference traverses up from
     scope foo3 to scope foo1 before finding the block foo2 and resolving the
     name. The LRM description doesn't cover this at all.
     
     I also don't think it specifies what should happen if a hierarchical name
     matches both an upward reference and a different full hierarchical reference.
     For example, if there is an additional top-level module in the previous
     example:
     
     module foo2;
     integer bar;
     endmodule
     
     Which one does the name foo2.bar resolve to?
     
     Steven Sharp
     sharp@cadence.com
     

    This archive was generated by hypermail 2.1.4 : Mon Apr 12 2004 - 15:10:12 PDT and
    sponsored by Boyd Technology, Inc.