Date: Tue May 22 2012 - 12:24:39 PDT
Your understanding matches mine. The value of m may be unexpected and not useful, but is not undetermined.
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Rich, Dave
Sent: Tuesday, May 22, 2012 2:39 PM
To: sv-ec@eda.org
Subject: [sv-ec] determinism of fork/join_none processes
This is from: http://verificationguild.com/modules.php?name=Forums&file=viewtopic&p=20425#20425
In this example from 9.3.2
initial
for( int j = 1; j <= 3; ++j )
fork
automatic int k = j; // local copy, k, for each value of j
#k $write( "%0d", k );
begin
automatic int m = j; // the value of m is undetermined
...
end
join_none
I think the value for all variables called m is deterministically 4 because the for loop must end, leaving j at 4 before any process can start. Mantis 652<http://www.eda.org/svdb/view.php?id=652> suggested that comment be deleted, but it was not. Am I missing something?
Dave Rich
Verification Technologist
Mentor Graphics Corporation
[cid:image001.png@01CD382F.00AF01A0]<http://www.twitter.com/dave_59>[cid:image002.png@01CD382F.00AF01A0]<http://go.mentor.com/drich>
-- 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.
