-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Do not allow JSON targets to set is-builtin: true #86062
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
Conversation
r? @estebank (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #85775) made this pull request unmergeable. Please resolve the merge conflicts. |
89eb14b
to
65c5182
Compare
☔ The latest upstream changes (presumably #86231) made this pull request unmergeable. Please resolve the merge conflicts. |
LLVM target name does not necessarily match the Rust target name and it can be confusing when the ICE message is describing a target other than has been specified on the command line.
r? rust-lang/compiler-contributors |
@bors r+ rollup |
📌 Commit f4701cd has been approved by |
☀️ Test successful - checks-actions |
Note that this will affect (and make builds fail for) all of the projects out there that have target files invalid in this way. Crater, however, does not really cover these kinds of the codebases, so it is quite difficult to measure the impact. That said, the target files invalid in this way can start causing build failures each time LLVM is upgraded, anyway, so it is probably a good opportunity to disallow this property, entirely.
Another approach considered was to simply not parse this field anymore, which would avoid making the builds explicitly fail, but it wasn't clear to me if
is-builtin
was always set unintentionally… In case this was the case, I'd expect people to file a feature request stating specifically for what purpose they were usingis-builtin
.Fixes #86017