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

Ensure child stack passed to clone is 16 byte aligned. #490

Merged
merged 1 commit into from
Dec 16, 2016
Merged

Ensure child stack passed to clone is 16 byte aligned. #490

merged 1 commit into from
Dec 16, 2016

Conversation

kevindejong
Copy link
Contributor

@kevindejong kevindejong commented Dec 11, 2016

The current implementation assumes that the array passed by the caller is word aligned (which I don't think Rust guarantees for [u8]) and a multiple of the word size.

@fiveop
Copy link
Contributor

fiveop commented Dec 16, 2016

I am not sure whether there are any platforms that need less then 16 byte alignment, however all should require a factor of 16, so this should at least not break anything and certainly improve things. (However, I think bionic on Android already does this in clone itself, for example.)

@homu +

@fiveop
Copy link
Contributor

fiveop commented Dec 16, 2016

@homu r+

@homu
Copy link
Contributor

homu commented Dec 16, 2016

📌 Commit 7b98f0d has been approved by fiveop

homu added a commit that referenced this pull request Dec 16, 2016
Ensure child stack passed to clone is 16 byte aligned.

The current implementation assumes that the array passed by the caller is word aligned (which I don't think Rust guarantees for [u8]) and a multiple of the word size.
@homu
Copy link
Contributor

homu commented Dec 16, 2016

⌛ Testing commit 7b98f0d with merge 5e932dc...

@homu
Copy link
Contributor

homu commented Dec 16, 2016

☀️ Test successful - status

@homu homu merged commit 7b98f0d into nix-rust:master Dec 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants