errata/234: 12.3.{2,3,6}, named port connections for implicit ports with same name

From: Brad Pierce (Brad.Pierce@synopsys.com)
Date: Wed Dec 25 2002 - 19:44:14 PST

  • Next message: Shalom.Bresticker@motorola.com: "errata/128: PROPOSAL - 10.3.5 Example: ram_model"

    Precedence: bulk

    >Number: 234
    >Category: errata
    >Originator: "Brad Pierce" <Brad.Pierce@synopsys.com>
    >Environment:
    >Description:

    According to section 12.3.2 --

      "Use of named port connections shall not be used for implicit
       ports unless the port_expression is a simple port_identifier."

    Could an instance of a module like same_input() from 12.3.3 be
    connected by name? --

       module same_input (a,a);
       input a; // This is legal. The inputs are tied together.
       ...

    For example, by

       same_input inst(.a(io1));

    Also, is it legal for explicit ports to have the same name,
    for example, --

       module same_input2 (.p(a),.p(a));
       input a;

    or
       module same_input3 (.p(a),.p(b));
       ...

    (In same_input3, a and b might even be of different sizes.)

    -- Brad

    This archive was generated by hypermail 2.1.4 : Wed Dec 25 2002 - 19:50:24 PST and
    sponsored by Boyd Technology, Inc.