The attached program demonstrates a problem that is only in development and appears to be caused by the fork/join rework done to support the new SystemVerilog join options. The comments explain what I have discovered. It looks like the disable is killing the second initial thread not just the named block. This can be worked around by swapping the order of the two items in the fork/join so I'm only raising the priority to 6 since it is giving invalid results without a warning. I'm assigning this to Steve since he was the author of the original changes.
Log in to post a comment.