[sv-bc] Mantis 2008

From: Bresticker, Shalom <shalom.bresticker_at_.....>
Date: Sun Jan 20 2008 - 23:41:43 PST
Comments on Mantis 2008:

1. First, a comment on Mantis 2131, which is referenced by 2008:

If the proposal renames the title of 12.4.2 from
"12.4.2 unique-if and priority-if"
to
"12.4.2 unique-if, unique0-if and priority-if",

then it should also rename the title of 12.5.3 from 
"12.5.3 unique-case and priority-case"
to
"12.5.3 unique-case, unique0-case and priority-case" 

2. A note to the editor says, 
"Changes to Mantis 2131 are only taken into account in the new wording,
not anywhere else."
The note should refer to Mantis 1345 as well.


3. In 12.4.2.1 and 12.5.3.1, after the first reference in each to the
"active region set", add "(see 4.4.1)".


4. In the unique-if example in 12.4.2.1,
always_comb begin : a1
unique if (a) begin : i1
z = a || b;
else if (not_a) begin
z = a || c;
end
end
there is an "end" missing after "begin :i1". Simpler would be

always_comb begin : a1
unique if (a) 
z = a || b;
else if (not_a) 
z = a || c;
end

5. 12.4.2.1 and 12.5.3.1 say in the examples, "the implied assertion
will fail". But nowhere is it stated that unique/priority if/case create
implied assertions. If the LRM is to require that they be treated as
assertions, that needs to be stated explicitly. The implications of that
need to be considered. For example, does $assertoff affect them?


6. Similarly, 12.4.2.1 and 12.5.3.1 do not specify how the immunity to
false errors is to be implemented, with what mechanism. The examples
talk about "flushing the original error", etc., but that is not a
normative specification of a requirement.

Shalom Bresticker
Intel Jerusalem LAD DA
+972 2 589-6582
+972 54 721-1033


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Sun Jan 20 23:45:09 2008

This archive was generated by hypermail 2.1.8 : Sun Jan 20 2008 - 23:45:43 PST