By time consuming, I meant in the latter sense primarily. Another way to think of it is that fork join_any/all can be potentially time consuming, but fork/join none statement can never be so regardless of where it is called, function or not. Regards, -Ambar -----Original Message----- From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Steven Sharp Sent: Thursday, February 16, 2006 2:14 PM To: Dave_Rich@mentor.com; sv-ec@eda.org; sv-bc@eda.org; ambar.sarkar@paradigm-works.com Subject: RE: [sv-ec] Can a function contain a fork/join/any/none? >From: "Ambar Sarkar" <ambar.sarkar@paradigm-works.com> >Is there a definition of the term "time consuming"? A fork/join none(not the >others) is non time consuming as far as I understand. The others are not "time consuming" either. They block to wait for one or all of their subprocesses to complete, but those subprocesses cannot consume time before completing, so that blocking does not consume any time. If you define "time consuming" to mean blocking to wait for something, even if that cannot consume any time, then you are correct. Both fork/join and fork/join_any will block, while fork/join_none will not. Steven Sharp sharp@cadence.comReceived on Thu Feb 16 13:43:37 2006
This archive was generated by hypermail 2.1.8 : Thu Feb 16 2006 - 13:43:50 PST