Rollup of PRs in the queue; Sunday #22909
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These implementations were temporary workaround. Now rust-lang#22828 has been fixed, they can be removed.
some commits in OpenBSD base have corrected a problem of stack position. Now, we can adjust more accurately the page guard in rust.
static_assert is documented as working on static with type `bool`, but we currently accept it on any const static and crash when the const has an non-integral type. This is a breaking-change for anyone who used static_assert on types likes i32, which happened to work but seems like an unintended consequence of the missing error checking. [breaking-change] Fixes rust-lang#22056
|
@bors: p=20 r+ |
1 similar comment
|
@bors: p=20 r+ |
bors
added a commit
that referenced
this pull request
Feb 28, 2015
The timing code break when using multiple codegen units, but that shouldn't stop us from using it with a single codegen unit.
|
💔 Test failed - auto-win-64-opt |
These implementations were temporary workaround. Now rust-lang#22828 has been fixed, they can be removed.
A misplaced uint->u32 instead of usize in fmt::Pointer. Added a basic test.
some commits in OpenBSD OS have corrected a problem of stack position. Now, we can adjust more accurately the page guard in rust. @dhuseby I am not sure that bitrig have already integrated these changes (the `$OpenBSD$` header in sys/kern/kern_exec.c is too old). But when they do, you may want this patch too.
static_assert is documented as working on static with type `bool`, but we currently accept it on any const static and crash when the const has an non-integral type. This is a breaking-change for anyone who used static_assert on types likes i32, which happened to work but seems like an unintended consequence of the missing error checking. [breaking-change] Fixes rust-lang#22056
|
@bors: r+ |
The markdown listing the link in [StrExt::width](http://doc.rust-lang.org/std/str/trait.StrExt.html#tymethod.width) isn't being parsed properly. I'm expecting it's because the `[ ]` is across 2 lines so this changes that. This is untested though.
The timing code break when using multiple codegen units, but that shouldn't stop us from using it with a single codegen unit.
bors
added a commit
that referenced
this pull request
Mar 1, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
r? @Manishearth