Subject: [sv-ec] Review comments from Jonathan Bradford.
From: David W. Smith (david.smith@synopsys.com)
Date: Mon Apr 07 2003 - 09:43:35 PDT
Greetings
Here are some further comments from one of the SV-EC reflector reviewers.
Likewise for the meeting today.
Remember, the meeting today will NOT make technical changes to the LRM
(unless a great faux pas has occurred). So, we are going to edit (as in
grammer, spelling, clarity, consistency) and not write (as in new material
or content change to existing material). (We do have some missing items that
we will have to handle such as operators missing from tables - a faux pas).
Regards
David
-----Original Message-----
From: bradford@Synopsys.COM [mailto:bradford@Synopsys.COM] On Behalf Of
Jonathan Bradford;Freiburg
Sent: Monday, April 07, 2003 2:28 AM
To: David W. Smith
Subject: Re: [sv-ec] Draft 4 LRM Issues
Hello David,
as a System Verilog observer, here are some corrections for Draft 4 (upto
section 10)
1) 3.7 Chandle, p11
define/clarify why chandle cannot be used in structures or unions
2) 3.8.9 atoi() & 3.8.11 itoa() p15
allow atoint() as alias for atoi() [ to complement atohex(), atooct()
& atobin() ]
3) 3.9 Event data type p16
in description, clarify if event data type can be passed through port
4) 4.2 Packed and unpacked arrays p29
Note: unpacked array size, a range[n:m] or a singular size [p] as range
shorthand ([p-1:0]) can be used to specify
dimension - the text does not say this - it says no range and singular
size only.
5) 4.7 Array assignment p33
p = {d[1:3],"hello", d[4:5]};
This is the basis of list and queue manipulation. Good. Can it be
extended to show pop ?
p = d[1:4]
Clarify that the dynamic array can be through an interface port.
Can there be queues of queues ?
How in above case can p be set to "a", "b", "c", "hello", "de"
i.e. p = {d[1:3], "hello", (d[4:5]) }; ?
as there may be an ambiguity in arrays of arrays and what is extending
what slices & elements ?
6) 4.8 Arrays as arguments p34
... passed arguments of compatible type and size ...
Compatible type does not mean identical type - i.e. assignment
compatible.
Hence fun(int a [3:1][3:1]);
actual reg b [3:1][3:1]; should work as the copied
values from reg to int are assignement compatible (x to 0 etc) ?
7) 4.10.1 num() p37
int imem[*];
$display (map.num);
imem or map variable ?
8) 7.5 Wild equality and wild inequality p52
operator !=== is a mistake surely, mean !== ?
also <= non-blocking assignemt operator missing from precedence table.
9) 9.6 fork join p71
function int wait_20; contains timing ! (// illegal note just
talks about fork/join & return)
10) 10.2 Tasks p76
formal arguments input, output, inout
add ref as a 4th style - reference 10.5.2 later
Do for functions too.
Hope this is of use to you
Jonathan Bradford
"David W. Smith" wrote:
Greetings,Just a reminder that I will be collecting ALL of the changes to
Draft 4. Please make sure that you email me your changes once you have
decided on them. I will then collected, organize, and submit them to Stu for
inclusion in Draft 5. There will be a website with all of the changes once I
start getting them in.RegardsDavid David W. Smith
Synopsys ScientistSynopsys, Inc.
Synopsys Technology Park
2025 NW Cornelius Pass Road
Hillsboro, OR 97124
Voice: 503.547.6467
Main: 503.547.6000
FAX: 503.547.6906
Email: david.smith@synopsys.com
http://www.synopsys.com <http://www.synopsys.com/>
--____________________________________________________________________________ ____
/\ Jonathan Bradford mailto:bradford@micronas.com
\/
/\/\ MICRONAS GmbH http://www.micronas.com
/\/\/\
\/\/\/ Hans-Bunte-Str.19 Tel: +49 (0)761 517 2884
\/\/ D-79108 Freiburg Fax: +49 (0)761 517 2880
\/ Germany
This archive was generated by hypermail 2b28 : Mon Apr 07 2003 - 09:44:23 PDT