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.

Sign up for GitHub

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

Scheduler should drop unrunnable tasks into the work queue instead of blocking on them #9831

Closed
larsbergstrom opened this issue Oct 12, 2013 · 1 comment
Closed

Scheduler should drop unrunnable tasks into the work queue instead of blocking on them #9831

larsbergstrom opened this issue Oct 12, 2013 · 1 comment

Comments

@larsbergstrom
Copy link
Contributor

See the example code shown in:
https://gist.github.com/ILyoan/6945608

The problem seems to be that when we use start_on_main_thread, any tasks subsequently spawned may be sent to the friend single threaded scheduler via a message, but they will not be made available for pickup by the work-stealing scheduler. This design prevents parallel speedups for the gist as written above. If it's switched to instead start the program from the normal #[main], spawn works more closely to expectations.
@sanxiyn sanxiyn mentioned this issue Oct 14, 2013
Closed
@Aatch
Copy link
Contributor

Aatch commented Mar 4, 2014

Looks like this was closed by #9857

@Aatch Aatch closed this as completed Mar 4, 2014
flip1995 pushed a commit to flip1995/rust that referenced this issue Nov 21, 2022
@kartva
fix never_loop false positive
9899861 
on unconditional break to internal labeled block

ref rust-lang#9831
flip1995 pushed a commit to flip1995/rust that referenced this issue Nov 21, 2022
@bors
Auto merge of rust-lang#9837 - DesmondWillowbrook:never_loop, r=dswij
a599527 
fix never_loop false positive

fixes rust-lang#9831

changelog: [`never_loop`]: fixed false positive on unconditional break in internal labeled block
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Aatch @larsbergstrom