-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
we don't detect LLVM needing a rebuild correctly in llvm-finished-building
#55537
Comments
Some potentially useful extra info:
|
backtrace from running under
|
hmm for some reason this system is using a I guess I should double-check this against a nightly that I download via |
yeah okay this doesn't occur on a nightly I downloaded via |
And unfortunately the debug does not replicate after I do a rebuild of LLVM with |
can't replicate anymore. :( I have a sneaking suspicion that this might be due to my build of LLVM being stale in some way? not sure. I sort of wish I had taken a snapshot of my directory structure at the time before I cleaned it as part of trying to test out alternate configurations... |
@pnkfelix Fwiw I have the same issue locally |
It is LLVM, I had these failures (all segfaults, i.e. "signal 11"):
And they were fixed by @alexcrichton @Mark-Simulacrum @rkruppe We should keep track of the fact that we don't detect LLVM needing a rebuild correctly. IMO |
rustc -Clto
segfaulting during compile of ui/issues/issue-44056.rsllvm-finished-building
Same issue here, with two separate rustc checkouts. Currently rebuilding LLVM to see if that helps. (Deleting that file triggered a complete rebuild.) |
Confirmed that rebuilding LLVM fixes the problem. |
replace llvm-rebuild-trigger with submodule commit hash As mentioned in #59285. This PR removes the need to update the `llvm-rebuild-trigger` file. Instead, the latest commit hash of the appropriate LLVM submodule will be stored in the stamp file and used to detect if a build is required. Fixes #42405. Fixes #54959. Fixes #55537.
fortunately:
cc #44056
The text was updated successfully, but these errors were encountered: