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

Make sure we do not create an unaligned slice #42

Merged
merged 2 commits into from
Aug 3, 2018

Conversation

RalfJung
Copy link
Contributor

@RalfJung RalfJung commented Aug 2, 2018

Based on discussion in rust-lang/rust#52972:

References have to be always aligned. This includes &[T], and it includes the case where the slice is empty. chunk_align was producing an unaligned mid part when the cmp::min(..., d2) picked the RHS.

So I pulled the conditional out of cmp::min, returning early if the slice is so short that the aligned beginning is beyond the end of the slice.

@Veedrac
Copy link
Collaborator

Veedrac commented Aug 2, 2018

Looks good to me, thanks for the patch.

Maybe an assert would be better than the comment? We can spare the cycles here.

@RalfJung
Copy link
Contributor Author

RalfJung commented Aug 3, 2018

Maybe an assert would be better than the comment? We can spare the cycles here.

Sure, done.

@Veedrac Veedrac merged commit 2283ec8 into llogiq:master Aug 3, 2018
@Veedrac
Copy link
Collaborator

Veedrac commented Aug 3, 2018

Thanks again 👍.

@llogiq Could we get a patch release for this? This shouldn't have actually caused any bad codegen but it'll help around rust-lang/rust#52972.

@llogiq
Copy link
Owner

llogiq commented Aug 3, 2018

I just published 0.3.2.

bors added a commit to rust-lang/rust that referenced this pull request Sep 16, 2018
stabilize slice_align_to

This is very hard to implement correctly, and leads to [serious bugs](llogiq/bytecount#42) when done incorrectly. Moreover, this is needed to be able to run code that opportunistically exploits alignment on miri. So code using `align_to`/`align_to_mut` gets the benefit of a well-tested implementation *and* of being able to run in miri to test for (some kinds of) UB.

This PR also clarifies the guarantee wrt. the middle part being as long as possible.  Should the docs say under which circumstances the middle part could be shorter? Currently, that can only happen when running in miri.
Centril added a commit to Centril/rust that referenced this pull request Jan 14, 2019
…r=alexcrichton

Add a debug_assert to Vec::set_len

Following the precedent of rust-lang#52972, which found llogiq/bytecount#42.

(This may well make a test fail; let's see what Travis says.)
Centril added a commit to Centril/rust that referenced this pull request Jan 14, 2019
…r=alexcrichton

Add a debug_assert to Vec::set_len

Following the precedent of rust-lang#52972, which found llogiq/bytecount#42.

(This may well make a test fail; let's see what Travis says.)
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.

3 participants