-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Is debug rustc + (Release+Asserts) llvm a valid bootstrap combination? #32706
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
Comments
I'm not sure what would cause this, but the most likely option is probably that your build is broken in some way. That function isn't conditionally compiled and the relevant file has the appropriate |
It would be helpful to know what LLVM you are using, since it doesn't seem to be the default one. |
That function is in |
Thanks, I must have broken something by trying to reuse an existing llvm build directory that I'd preserved. It normally works for the same build type but this time it was changed to debug. The only other potential problem could be the edit |
Turned out I wasn't doing anything wrong but my local clone got corrupted somehow. It took ages to produce this trace on ARM but it might help unravel the mystery of the |
If not, fine, otherwise here's a bug:
The reason I'm asking this (looks like a regular name resolution error), is the
cfg: disabling C++ optimization (CFG_DISABLE_OPTIMIZE_CXX)
option, which is not true in this case, as I was using an existing llvm build.Source revision:
a09f386
The text was updated successfully, but these errors were encountered: