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

support alloca #6203

Closed
thestinger opened this issue May 3, 2013 · 6 comments
Closed

support alloca #6203

thestinger opened this issue May 3, 2013 · 6 comments
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.

Comments

@thestinger
Copy link
Contributor

It's probably going to be tricky to get this working with the segmented stack implementation.
@pcwalton
Copy link
Contributor

pcwalton commented May 3, 2013

I think it's impossible to get that working.

@pcwalton pcwalton closed this as completed May 3, 2013
@pcwalton
Copy link
Contributor

pcwalton commented May 3, 2013

Well, I'll reopen in case there is some way I hadn't thought of.

@pcwalton pcwalton reopened this May 3, 2013
@brson
Copy link
Contributor

brson commented Jun 27, 2013

The full gcc __morestack implementation does allow for dynamically sized frames. It inserts calls to yet another __morestack function before alloca-ing. I don't particularly want to support it though.

@pnkfelix
Copy link
Member

Visiting for bug triage, email from 2013-08-12.

Nothing to add (wish list tag seems appropriate for now).

@thestinger
Copy link
Contributor Author

There are no more segmented stacks, so supporting this seems very feasible. It could be implemented with a wrapper function performing a stack overflow check inside.

@steveklabnik steveklabnik mentioned this issue Jan 21, 2015
Closed
@steveklabnik
Copy link
Member

I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized.

This issue has been moved to the RFCs repo: rust-lang/rfcs#618

bors added a commit to rust-lang-ci/rust that referenced this issue Oct 24, 2020
@bors
Auto merge of rust-lang#6203 - giraffate:fix_link_to_labeled_issues, …
fbe75a8 
…r=Manishearth

Fix links to labeled issues

These labels seems wrong.
- <https://github.com/rust-lang/rust-clippy/labels/L-crash%20%3Aboom%3A>
- <https://github.com/rust-lang/rust-clippy/labels/L-bug%20%3Abeetle%3A>

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@steveklabnik @brson @pcwalton @pnkfelix @thestinger