-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
LLVM assertion hit when bootstrapping with a local rustc ("Invoking a function with bad signature") #12115
Comments
This is probably because the signatures of lang items have changed between the stage0 snapshot and the current commit and we don't type check them (#9307), so the local-rust compiler is generating calls to the stage0 functions which differ from the stage1/stage2 functions. Running with |
I think that you may have got this right, and this could be related to different arity of I managed to get some output from From what I can understand, this is getting stuck in the middle of |
So, this is happening due to the recently landed #12059. I'll wait for the next snapshot to happen and the legacy removed before trying again. |
Closing, this is just a relic of the local rust root not being the exact snapshot that we currently need. We could verify that |
I'm currently trying to bootstrap current rust from a system-installed copy of itself, by doing firstly a normal installation and then the second one using
--enable-local-rust
. However the build fails on libstd, triggering a LLVM assertion in rustc. Both local-stage0 and source tree are at 548b8ce.Build failure:
Assertion backtrace:
System is an amd64 debian wheezy (stable 7.1), using gcc-4.7 and rust embedded LLVM copy. Is there any way to get more debug info on rust side?
The text was updated successfully, but these errors were encountered: