You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
llvm::StructType::getElementType: Assertion `N < NumContainedTys && "Element number out of range!"' failed. #21721
rustc: /build/rust-git/src/rust/src/llvm/include/llvm/IR/DerivedTypes.h:285: llvm::Type* llvm::StructType::getElementType(unsigned int) const: Assertion `N < NumContainedTys && "Element number out of range!"' failed.
Aborted (core dumped)
This is actually happening inside LLVM optimizations, in the early-cse pass (-C opt-level=1 still triggers it). Originally found in a memcpy optimized into a load.
Reduced LLVM IR:
This needs a test, and there's also two hacks introduced by #21744, that should be reverted now that the LLVM bug is fixed (they both reference this issue).
I guess you get that in stage0? That will need a new snapshot, so that the
stage0 compiler also uses the new LLVM
Am 26.02.2015 20:40 schrieb "Piotr Czarnecki" notifications@github.com:
Activity
eddyb commentedon Jan 28, 2015
Current LLVM fork tip: rust-lang/llvm@b820135 on top of llvm-mirror/llvm@0ad623b.
dotdash commentedon Feb 15, 2015
http://llvm.org/bugs/show_bug.cgi?id=22595
Update LLVM to rust-llvm-2015-02-19
Update LLVM to rust-llvm-2015-02-19
Auto merge of #22526 - dotdash:llvmup, r=alexcrichton
7 remaining items
eddyb commentedon Feb 24, 2015
This needs a test, and there's also two hacks introduced by #21744, that should be reverted now that the LLVM bug is fixed (they both reference this issue).
dotdash commentedon Feb 24, 2015
@eddyb will you take care of that?
Rollup merge of rust-lang#22837 - eddyb:issue-21721, r=dotdash
pczarn commentedon Feb 26, 2015
I'm still getting this failure in #21973 during the compilation of rustc-trans
dotdash commentedon Feb 27, 2015
I guess you get that in stage0? That will need a new snapshot, so that the
stage0 compiler also uses the new LLVM
Am 26.02.2015 20:40 schrieb "Piotr Czarnecki" notifications@github.com: