Re: [sv-ac] Updated proposal for 3069

I understand that regular clocking still can be declared inside generate
only global clocking would be illegal

There is also not resolved simialr issue in mantis for default clocking
and generates
http://www.verilog.org/mantis/view.php?id=3515

DANiel

On 11/16/2011 4:47 PM, ben cohen wrote:
> I think that it would be a good idea to add a note on how to handle
> global clocking using parameters, as we discussed at our meeting:
>
> parameter P;
> generate
> if (P==1) begin:b1
> assign gen_clk = clk1;
> end
> else begin:b1
> assign gen_clk = clk2;
> end
> endgenerate
>
> global_clocking b1.gen_clk;
>
>
> On Wed, Nov 16, 2011 at 3:54 AM, Kulshrestha, Manisha
> <Manisha_Kulshrestha@mentor.com
> <mailto:Manisha_Kulshrestha@mentor.com>> wrote:
>
> Hi Jacob,
>
> I think it is better to phrase it like this:
>
> Global clocking may be declared in a module, an interface, a
> checker, or a program. A given module, interface, checker, or
> program mayshall contain at most one global clocking declaration;
> it shall be an error otherwise. Global clocking shall not be
> declared in a generate block.
>
> Thanks.
>
> Manisha
>
> *From:*owner-sv-ac@eda.org <mailto:owner-sv-ac@eda.org>
> [mailto:owner-sv-ac@eda.org <mailto:owner-sv-ac@eda.org>] *On
> Behalf Of *Katz, Jacob
> *Sent:* Wednesday, November 16, 2011 2:50 PM
> *To:* sv-ac@eda-stds.org <mailto:sv-ac@eda-stds.org>
> *Subject:* [sv-ac] Updated proposal for 3069
>
> Following the recent discussion, I uploaded a modified proposal
> for 3069 which disallows global clocking declaration in generate
> blocks.
>
> Please review at http://www.eda-stds.org/mantis/view.php?id=3069.
>
> The changes are as follows.
>
> * Replaced:
>
> Global clocking may be declared in a module, an interface, a
> checker, or a program, including inside a generate block therein.
> A given module, interface, checker, or program may contain
> multiple global clocking declarations appearing syntactically, for
> example within generate conditionals. However, any of its
> instances in the elaborated design description shall contain at
> most one global clocking declaration; it shall be an error otherwise.
>
> With:
>
> Global clocking may be declared in a module, an interface, a
> checker, or a program. A given module, interface, checker, or
> program may contain at most one global clocking declaration; it
> shall be an error otherwise. Global clocking shall not be declared
> in a generate block.
>
> * Removed references to generate blocks from the hierarchical
> lookup rules.
>
> * Removed the last two examples
>
> --------------------------------
>
> *Jacob M. Katz*| jacob.katz@intel.com
> <mailto:jacob.katz@intel.com> | *Work:* +972-4-865-5726
> <tel:%2B972-4-865-5726> | *iNet: *(8)-465-5726
>
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>,
> and is
> believed to be clean.
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>,
> and is
> believed to be clean.
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.