Subject: Re: [vhdl-200x] Re: Fork/Join
From: vhdl-200x@grfx.com
Date: Mon Jun 09 2003 - 13:02:27 PDT
> From: Wolfgang Roethig <wroethig@necelam.com>
>
> "Fork" and "join" is actually Verilog 95.
> Statements enclosed by "fork" and "join" are
> executed concurrently, whereas statements
> enclosed by "begin" and "end" are executed
> sequentially.
Yes, but SV added "join_any" and "join_none" which
lets you create any number of new threads dynamically
(previously the threads would be gathered at the join
before you can re-execute the fork so there was a static
limit).
I think you can get the equivalent behavior with Peter's
suggestion and a loop.
BTW, Posix thread info is available at -
http://www.humanfactor.com/pthreads/pthreadlinks.html
Kev.
> Since translators and simulators with dual
> language support have been around for a while,
> the VHDL equivalent of "fork" and "join" should
> already exist. No need to extend VHDL for this
> feature.
>
> People have argued that VHDL has already
> a richer description capability than Verilog,
> and SystemVerilog basically catches up with VHDL.
>
> Therefore my recommendation is to establish a
> correspondence between VHDL and SystemVerilog first
> before creating a list of required VHDL enhancements.
>
> Wolfgang
>
> > X-Authentication-Warning: server.eda.org: wroethig set sender to
> owner-vhdl-200x@server.eda.org using -f
> > Date: Sun, 8 Jun 2003 10:44:44 -0700 (PDT)
> > From: vhdl-200x@grfx.com
> > To: vhdl-200x@eda.org
> > Subject: [vhdl-200x] Re: Fork/Join
> > X-Spam-Status: No, hits=0.7 required=5.0 tests=NO_REAL_NAME version=2.52
> > X-Spam-Level:
> > X-Spam-Checker-Version: SpamAssassin 2.52 (1.174.2.8-2003-03-24-exp)
> > X-Loop: wroethig@eda.org
> >
> >
> > I noticed that adding fork/join (a la SystemVerilog) was on
> > someone's list of enhancements. I would highly recommend not
> > adding fork/join and instead just add a means of creating
> > single threads dynamically and add proper thread control
> > in the style of the Posix threads library - the fork/join
> > syntax doesn't lend itself to capturing thread identifiers
> > and makes fine-grained control difficult.
> >
> > Kev.
> >
>
This archive was generated by hypermail 2b28 : Mon Jun 09 2003 - 13:14:15 PDT