Update compiler-builtins and use it in the 128-bit lowering MIR test#46290
Update compiler-builtins and use it in the 128-bit lowering MIR test#46290bors merged 4 commits intorust-lang:masterfrom
Conversation
There was a problem hiding this comment.
This feature attribute can be removed now.
|
r? @nagisa |
|
☔ The latest upstream changes (presumably #46142) made this pull request unmergeable. Please resolve the merge conflicts. |
9fb05b3 to
c80fee2
Compare
|
@bors r+ |
|
📌 Commit c80fee2 has been approved by |
|
⌛ Testing commit c80fee2 with merge 47e2cd3b8b0132edd39291a88110a2789157e6e2... |
|
💔 Test failed - status-travis |
|
I don't think I caused this? [00:12:56] In file included from /Users/travis/build/rust-lang/rust/src/llvm/lib/Support/ThreadPool.cpp:14:
[00:12:56] In file included from /Users/travis/build/rust-lang/rust/src/llvm/include/llvm/Support/ThreadPool.h:30:
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:1447:23: error: 'future_error' is unavailable: introduced in macOS 10.8
[00:12:56] future_error(make_error_code(future_errc::broken_promise))
[00:12:56] ^
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:502:63: note: 'future_error' has been explicitly marked unavailable here
[00:12:56] class _LIBCPP_EXCEPTION_ABI _LIBCPP_AVAILABILITY_FUTURE_ERROR future_error
[00:12:56] ^
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:1621:23: error: 'future_error' is unavailable: introduced in macOS 10.8
[00:12:56] future_error(make_error_code(future_errc::broken_promise))
[00:12:56] ^
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:502:63: note: 'future_error' has been explicitly marked unavailable here
[00:12:56] class _LIBCPP_EXCEPTION_ABI _LIBCPP_AVAILABILITY_FUTURE_ERROR future_error
[00:12:56] ^
[00:12:56] 2 errors generated. |
|
@bors retry
Let's see what happens. I doubt it is this patch as well.
…On Nov 29, 2017 7:23 AM, "scottmcm" ***@***.***> wrote:
I don't think I caused this?
[00:12:56] In file included from /Users/travis/build/rust-lang/rust/src/llvm/lib/Support/ThreadPool.cpp:14:
[00:12:56] In file included from /Users/travis/build/rust-lang/rust/src/llvm/include/llvm/Support/ThreadPool.h:30:
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:1447:23: error: 'future_error' is unavailable: introduced in macOS 10.8
[00:12:56] future_error(make_error_code(future_errc::broken_promise))
[00:12:56] ^
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:502:63: note: 'future_error' has been explicitly marked unavailable here
[00:12:56] class _LIBCPP_EXCEPTION_ABI _LIBCPP_AVAILABILITY_FUTURE_ERROR future_error
[00:12:56] ^
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:1621:23: error: 'future_error' is unavailable: introduced in macOS 10.8
[00:12:56] future_error(make_error_code(future_errc::broken_promise))
[00:12:56] ^
[00:12:56] /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/future:502:63: note: 'future_error' has been explicitly marked unavailable here
[00:12:56] class _LIBCPP_EXCEPTION_ABI _LIBCPP_AVAILABILITY_FUTURE_ERROR future_error
[00:12:56] ^
[00:12:56] 2 errors generated.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46290 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AApc0gwjM3WyYn6Oz6t88F3SusacO3daks5s7Oo-gaJpZM4Qq_qk>
.
|
|
⌛ Testing commit c80fee2 with merge fe78375574f2c9372a0140222773ec6a65067654... |
|
I should have looked at the queue; it seems to be a systemic thing as all the last 8 PRs failed on xcode 7.3: https://travis-ci.org/rust-lang/rust/builds |
|
💔 Test failed - status-travis |
|
@bors retry — travis-ci/travis-ci#8821 |
…s, r=nagisa Update compiler-builtins and use it in the 128-bit lowering MIR test This picks up the lang item implementations from rust-lang/compiler-builtins#210 cc rust-lang#45676 @est31 @nagisa
…s, r=nagisa Update compiler-builtins and use it in the 128-bit lowering MIR test This picks up the lang item implementations from rust-lang/compiler-builtins#210 cc rust-lang#45676 @est31 @nagisa
…s, r=nagisa Update compiler-builtins and use it in the 128-bit lowering MIR test This picks up the lang item implementations from rust-lang/compiler-builtins#210 cc rust-lang#45676 @est31 @nagisa
…s, r=nagisa Update compiler-builtins and use it in the 128-bit lowering MIR test This picks up the lang item implementations from rust-lang/compiler-builtins#210 cc rust-lang#45676 @est31 @nagisa
|
Tests from this PR caused the latest rollup to fail in asm.js due to
Details@bors r- |
T_T @scottmcm one of the ideas on how to deal with targets as broken as this was to:
I think the ideal place to do that is in the same place where ABI is handled. Do you agree @eddyb? |
|
For now, ignore the tests for emscripten targets altogether. The issue seems to be not present in the LLVM 5.0 WASM target. |
c80fee2 to
ad2a8e8
Compare
|
Updated; let me know if |
|
@bors r+ |
|
📌 Commit c0654ce has been approved by |
Update compiler-builtins and use it in the 128-bit lowering MIR test This picks up the lang item implementations from rust-lang/compiler-builtins#210 cc #45676 @est31 @nagisa
|
☀️ Test successful - status-appveyor, status-travis |
This picks up the lang item implementations from rust-lang/compiler-builtins#210
cc #45676 @est31 @nagisa