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

Remove stack alignment from core::task::unsafe_spawn_inner #1324

Closed
brson opened this issue Dec 17, 2011 · 0 comments
Closed

Remove stack alignment from core::task::unsafe_spawn_inner #1324

brson opened this issue Dec 17, 2011 · 0 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Dec 17, 2011

Pretty sure that aligning here has no effect since the setup in context::call does its own alignment.
@brson brson closed this as completed Dec 20, 2011
boggle pushed a commit to boggle/rust that referenced this issue Dec 20, 2011
@brson
libcore: Remove stack alignment from task spawning
586281e 
This is already done by the native task start code. Closes rust-lang#1324
@jyn514 jyn514 mentioned this issue Mar 25, 2021
Merged
@jyn514 jyn514 mentioned this issue Apr 2, 2021
Open
3 tasks
bjorn3 added a commit to bjorn3/rust that referenced this issue Mar 15, 2023
@bjorn3
Handle wrappers around dyn* in receiver types
ef6df7e 
Fixes rust-lang#1324
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@owenthewizard
Fix typo --lock -> --locked (rust-lang#1324)
e2e786c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brson