Update compiler-rt to fix MIPS64 infinite recursion #37849
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
|
@bors: r+ |
|
📌 Commit 8aef933 has been approved by |
|
⌛ Testing commit 8aef933 with merge ce4aa32... |
|
💔 Test failed - auto-win-msvc-64-cargotest |
|
Ouch, the CI failure is definitely legit. Bitten by a pretty obscure C preprocessor feature. |
xen0n
force-pushed
the
compiler-rt-bump
branch
from
8aef933 to
d37c025
Compare
|
(ping) |
|
@bors: r+ Oh sorry! Feel free to ping a PR whenever you update it, it seems GitHub doesn't always send out notifications... |
|
📌 Commit d37c025 has been approved by |
bors
added a commit
that referenced
this pull request
Nov 24, 2016
Update compiler-rt to fix MIPS64 infinite recursion Fixes #37823. Test fixes are coming in a separate PR later. r? @alexcrichton
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.
Fixes #37823.
Test fixes are coming in a separate PR later.
r? @alexcrichton