| Add Proposal | Add Analysis | Edit Class, Environment, or Release |
| Number | 452
|
| Category | errata
|
| Synopsis | 10.2.2, 10.3.1: 'reg' keyword in tf port declarations
|
| State | open
|
| Class | errata-simple
|
| Arrival-Date | Aug 27 2003
|
| Originator | "Brad Pierce" <Brad.Pierce@synopsys.com>
|
| Release | 2001b: 10.2.2, 10.3.1
|
| Environment |
204,227,233,234,292,332,345,452 |
| Description |
Does it change the meaning of a tf_input_declaration, tf_output_declaration or tf_inout_declaration to add the optional keyword 'reg'? Is there any difference, for example, between input reg [31:0] tics ; and input [31:0] tics ; or between (input reg a, b, c) and (input a, b, c) ? -- Brad |
| Fix |
|
| Audit-Trail |
From: Shalom Bresticker <Shalom.Bresticker@motorola.com> To: Brad Pierce <Brad.Pierce@synopsys.com> Cc: etf-bugs@boyd.com Subject: Re: errata/452: 10.2.2, 10.3.1 -- 'reg' keyword in tf port declarations Date: Thu, 28 Aug 2003 09:36:44 +0300 > Does it change the meaning of a tf_input_declaration, > tf_output_declaration or tf_inout_declaration to add > the optional keyword 'reg'? It appears not. In fact, the LRM does not, but should, discuss the meaning of type declarations of task/func arguments, and what happens if they are not explicitly declared. This is important because in a module, an input and an inout cannot be a reg, whereas in task/func's, you cannot have wires. -- Shalom Bresticker Shalom.Bresticker@motorola.com Design & Reuse Methodology Tel: +972 9 9522268 Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890 POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478 |
| Unformatted |
|
Hosted by Boyd Technology