Reply from Martin Stolpe
--------------------
Hi,
thanks a lot for your replies so far!
Jerry, this is some really nice example you have attached! This example doe=
s even more than what I was thinking of. I just wanted to start the threads=
but I wasn't sure how the joining of the threads should look like. The pos=
sibility to wait on either one thread to finish or to wait for all threads =
to finish is really great.
The idea in my mind was rather vague. I'm currently working on a testbench =
which should check the startup behavior of a component. There a several han=
dshakes which are running in parallel and which I wanted to test. So the se=
quential behavior of the component looks like this:
1. test reset behavior
2. set several registers in parallel: for that I wanted to use proced=
ures which implement the signal pattern needed for transferring the data; t=
he pattern is the same for all registers
3. send another configuration or more to the registers used in 2.
As the patterns are the same for all the registers it seemed logical to use=
procedures for that. But as the procedures are using wait statements I was=
n't able to use them in the process because they need to be executed in par=
allel.
So the question is: is there a good way to implement this using the current=
VHDL standard (then the discussion should be switched to one of the other =
mailing lists mentioned), or is this something which is worth to be thought=
about for the next revision of the VHDL standard?
Best regards
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Feb 16 09:45:20 2012
This archive was generated by hypermail 2.1.8 : Thu Feb 16 2012 - 09:46:00 PST