Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assertion failure on LLVM >= 3.5 #8999

Closed
Keno opened this issue Nov 13, 2014 · 3 comments
Closed

Assertion failure on LLVM >= 3.5 #8999

Keno opened this issue Nov 13, 2014 · 3 comments
Labels
kind:upstream The issue is with an upstream dependency, e.g. LLVM

Comments

@Keno
Copy link
Member

Keno commented Nov 13, 2014

The recent call work has exposed an assertion failure in LLVM:

Assertion failed: ((I.atEnd() || std::next(I) == def_instr_end()) && "getVRegDef assumes a single definition or no definition"), function getVRegDef, file /Users/kfischer/julia/deps/llvm-svn/lib/CodeGen/MachineRegisterInfo.cpp, line 306 

Tracking upstream issue http://llvm.org/bugs/show_bug.cgi?id=21557 and patch at http://reviews.llvm.org/D6245. If we want to support 3.5, we'll probably have to backport the patch.
Just filling this issue so people running into it can find it when searching.

@Keno Keno added the kind:upstream The issue is with an upstream dependency, e.g. LLVM label Nov 13, 2014
@ViralBShah
Copy link
Member

Is our current plan to move to LLVM 3.5 with our own patches, or to wait for LLVM 3.6?

@tkelman
Copy link
Contributor

tkelman commented Nov 19, 2014

Any patches we want to try to backport in LLVM before 3.5.1, we have about a week: http://article.gmane.org/gmane.comp.compilers.llvm.devel/78752

@tkelman tkelman mentioned this issue Dec 13, 2014
19 tasks
@Keno
Copy link
Member Author

Keno commented Dec 28, 2014

Committed upstream as http://reviews.llvm.org/rL224884 with a followup fix in http://reviews.llvm.org/rL22490.

@Keno Keno closed this as completed Dec 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:upstream The issue is with an upstream dependency, e.g. LLVM
Projects
None yet
Development

No branches or pull requests

3 participants