Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support fork-joins and time delays #235

Closed
veripoolbot opened this issue Apr 7, 2010 · 2 comments
Closed

Support fork-joins and time delays #235

veripoolbot opened this issue Apr 7, 2010 · 2 comments
Labels
effort: weeks Expect this issue to require weeks or more of invested effort to resolve type: feature-IEEE Request to add new feature, described in IEEE 1800

Comments

@veripoolbot
Copy link
Contributor

Author Name: Shankar Giri
Original Redmine Issue: 235 from https://www.veripool.org
Original Date: 2010-04-07

Filing separate bug as mentioned in #�. This is a pre-requisite to finally support timing events, loops and behavioral events.
@veripoolbot
Copy link
Contributor Author

Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-04-07T13:24:31Z

A real event loop, #�, is needed first.

My thought here is that rather than making threads, to convert fork/join with delays
to state machines (one per branch). This may not allow as much dynamic control, but
it is hundreds of times faster in execution.

More details when Shankar or someone is ready to work on it.

@veripoolbot veripoolbot added effort: weeks Expect this issue to require weeks or more of invested effort to resolve type: feature-IEEE Request to add new feature, described in IEEE 1800 labels Dec 22, 2019
@wsnyder wsnyder mentioned this issue Mar 28, 2021
Closed
@wsnyder
Copy link
Member

wsnyder commented Aug 30, 2022

In develop-v5.

@wsnyder wsnyder closed this as completed Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: weeks Expect this issue to require weeks or more of invested effort to resolve type: feature-IEEE Request to add new feature, described in IEEE 1800
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wsnyder @veripoolbot