Skip to content

Pointers stored on the stack aren't word-aligned #151

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Closed
pcwalton opened this issue Aug 20, 2010 · 2 comments
Closed

Pointers stored on the stack aren't word-aligned #151

pcwalton opened this issue Aug 20, 2010 · 2 comments

Comments

@pcwalton
Copy link
Contributor

Currently, pointers stored on the stack aren't word-aligned. This is a critical issue because it causes stack growth to fail most of the time.
@pcwalton
Copy link
Contributor Author

Commit fac28ad disables task growth for now until this is fixed.

@graydon
Copy link
Contributor

graydon commented Jan 27, 2011

WONTFIX (moot point given disabled stack growth)

mbrubeck pushed a commit to mbrubeck/rust that referenced this issue Oct 17, 2011
@pcwalton
Disable task-growing logic for now until rust-lang#151 is fixed
fac28ad
Aaron1011 pushed a commit to Aaron1011/rust that referenced this issue Oct 26, 2020
@bjorn3
Merge pull request rust-lang#151 from bjorn3/dependabot/cargo/ar-0.6.1
b337695 
Bump ar from 0.6.0 to 0.6.1
djtech-dev pushed a commit to djtech-dev/rust that referenced this issue Dec 9, 2021
@TheDan64
Merge pull request rust-lang#151 from willtunnels/build_malloc-fix
52c7a3d 
Build malloc fix
antoyo added a commit to antoyo/rust that referenced this issue Jun 7, 2022
@antoyo
Merge pull request rust-lang#151 from GuillaumeGomez/x86-intrinsics
0237d95 
Add intrinsic translation for x86 arch
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@danielsn @tedinski
Correctly handle the abort intrinsic (rust-lang#151)
ea22451
celinval added a commit to celinval/rust-dev that referenced this issue Nov 20, 2024
@celinval
Add a new challenge to verify CStr (rust-lang#151)
90d304b 
Proposes a new challenge to verify the safety of `CStr` implementation.

---------
Co-authored-by: Zyad Hassan <88045115+zhassan-aws@users.noreply.github.com>
This issue was closed.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@graydon @pcwalton