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 assertion failure after activating LTO on aarch64-apple-darwin #78881
changed the title [-]LTO encounters LLVM assertion failure on aarch64-apple-darwin[/-][+]LLVM assertion failure after activating LTO on aarch64-apple-darwin[/+]on Nov 11, 2020
@alexcrichton pointed out that it's likely not LTO itself that is at fault, just that the output of the LTO pass isn't well handled by a subsequent pass. They suggested to save the LLVM output and reduce it down:
I've opened https://bugs.llvm.org/show_bug.cgi?id=48188 as I think there's still an LLVM issue, even though my specific case appears to disappear on LLVM trunk. I do have an LLVM patch that allows the Rust testsuite to pass, however, so that's encouraging.
Activity
[-]LTO encounters LLVM assertion failure on aarch64-apple-darwin[/-][+]LLVM assertion failure after activating LTO on aarch64-apple-darwin[/+]shepmaster commentedon Nov 11, 2020
@alexcrichton pointed out that it's likely not LTO itself that is at fault, just that the output of the LTO pass isn't well handled by a subsequent pass. They suggested to save the LLVM output and reduce it down:
Using bugpoint reduced this a good amount:
Next steps are to see if this fails on LLVM master and either file a bug or try to find the commit that fixes it.
shepmaster commentedon Nov 12, 2020
Bisecting points to llvm/llvm-project@db464a3, which does mention aarch64, so next step is to attempt backporting and seeing what happens.
shepmaster commentedon Nov 16, 2020
I've opened https://bugs.llvm.org/show_bug.cgi?id=48188 as I think there's still an LLVM issue, even though my specific case appears to disappear on LLVM trunk. I do have an LLVM patch that allows the Rust testsuite to pass, however, so that's encouraging.
igxactly commentedon Mar 8, 2021
@shepmaster The LLVM issue you opened seems to be marked as resolved.
https://bugs.llvm.org/show_bug.cgi?id=48188#c5
llvm/llvm-project@c35761d
https://reviews.llvm.org/D92446
shepmaster commentedon Mar 8, 2021
Yep! @nikic fixed it. Superseded by #81451