BTW, I've noticed another minor issue with the text below. The variables in the example are unpacked arrays and the names of the variables explicitly underscore this fact. Those variables are later used in other examples in the same LRM section. However, in the latest LRM version, there is no restriction on the arrays to be unpacked to allow their usage with assignment patterns. The fact that all examples use variables that include "unpacked" word in their names may confuse the readers into thinking that variables have to be unpacked arrays. So it will be better to change the names of those variables. --Yulik. ________________________________ From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Feldman, Yulik Sent: Thursday, April 27, 2006 9:32 AM To: sv-bc@server.eda.org Subject: FW: [sv-bc] minor correction on size warnings in assignment patterns I've reported this as 1444. ________________________________ From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Feldman, Yulik Sent: Wednesday, April 26, 2006 8:30 AM To: sv-bc@server.eda.org Subject: [sv-bc] minor correction on size warnings in assignment patterns Hi, IEEE P1800-2005 Section 8.13.1 "Array assignment patterns" says: "Each expression item shall be evaluated in the context of an assignment to the type of the corresponding element in the array. In other words, the following examples do not give size warnings, unlike the similar assignments above: bit unpackedbits [1:0] = '{1,1}; // no size warning as bit can be set to 1 int unpackedints [1:0] = '{1'b1, 1'b1}; // no size warning as int can be // set to 1'b1" Also, IEEE P1364-2005 Section 5.6 "Assignments and truncation" says: "Implementations are not required to warn or report any errors related to assignment size-mismatch or truncation." Which means that issuing a warning/error is not required, but possible. So, shouldn't the text in P1800 read "the following examples do not have to give size warnings" instead of "the following examples do not give size warnings", which sounds as a requirement not to issue a warning/error? Thanks, Yulik.Received on Thu Apr 27 02:59:19 2006
This archive was generated by hypermail 2.1.8 : Thu Apr 27 2006 - 02:59:27 PDT