about summary refs log tree commit diff
path: root/src/rustllvm/RustWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2016-02-20 02:52:01 +0000
committerbors <bors@rust-lang.org>2016-02-20 02:52:01 +0000
commita212264011289885bdb8b2306a8fdd50e1f83c99 (patch)
tree6b2e9d0f5f6a26c4e37dcc929506d57d1d44c997 /src/rustllvm/RustWrapper.cpp
parent54f3f2e302d6e5460e14c7e21c2c1a54291e8a59 (diff)
parentd835f5bfd84104477d77cfc47e1f7a8c50ec384d (diff)
downloadrust-a212264011289885bdb8b2306a8fdd50e1f83c99.tar.gz
rust-a212264011289885bdb8b2306a8fdd50e1f83c99.zip
Auto merge of #31771 - alexcrichton:oops-that-didnt-fix-anything, r=brson
In #31717 we rebased our LLVM fork over the 3.8 release branch, and it was
thought that this fixed #31702. The testing, however, must have been erroneous,
as it unfortunately didn't fix the issue! Our MUSL nightly builders are failing
from the same assertion reported in the issue, so we at least know the test case
is a reproduction!

I believe the failure is only happening on the MUSL nightly builders because
none of the auto builders have LLVM assertions enabled, and the Linux nightly
builder *does* have assertions enabled for the binaries we generate but the
distcheck run doesn't test a compiler with LLVM assertions enabled.
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions