-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
ICE: Featuring core
in std
makes compiler go sideways
#91767
Comments
Hmm, I wonder if this ICE is related to #91715. @workingjubilee can you try cherry-picking that PR (it just changes one line) and see if it fixes it? |
No love: that doesn't even seem to change the errors in a discernible way. |
Running this on latest master (229d0a9) does not produce the error above for me with x.py check or x.py build. So potentially this is fixed, or the diff above is incomplete? Potentially your config.toml might be relevant as well. |
huh. it looks like my config.toml is # Includes one of the default files in src/bootstrap/defaults
profile = "library"
changelog-seen = 2 which is probably wrong, but I am not sure in what way, honestly. |
The profile line essentially copies this into your config: # These defaults are meant for contributors to the standard library and documentation.
[build]
# When building the standard library, you almost never want to build the compiler itself.
build-stage = 0
test-stage = 0
bench-stage = 0
[rust]
# This greatly increases the speed of rebuilds, especially when there are only minor changes. However, it makes the initial build slightly slower.
incremental = true
[llvm]
# Will download LLVM from CI if available on your platform.
download-ci-llvm = "if-available" |
Even with that config.toml, I'm still not able to reproduce this on 229d0a9. Can you re-verify, and perhaps paste a full log from x.py, rather than just the ICE? It's not impossible, I suppose, that this is somehow related to incremental. |
Huh, entirely possible. Lemme try with a fresh clone on my end. |
Huuuh. |
On Zulip, I was told this should "just work" by @Mark-Simulacrum. It does not and in fact ICEs, so I am reporting it as a bug for others to investigate at their leisure. @camelid might also be interested. 🤷
Code
This is provoked by applying the following diff and invoking
x.py check
.Meta
This is an issue during bootstrapping the compiler. The build was based on e6b883c.
Error output
Backtrace
The text was updated successfully, but these errors were encountered: