-
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
Rollup of 15 pull requests #100677
Rollup of 15 pull requests #100677
Conversation
Just moving code around so that triagebot can ping relevant parties when translation logic is modified. Signed-off-by: David Wood <david.wood@huawei.com>
Add mention groups to `triagebot.toml` for diagnostic derive macros and diagnostic translation sources/resources. Signed-off-by: David Wood <david.wood@huawei.com>
Instruct triagebot to autolabel pull requests that modify the translation sources with the `A-translation` label. Signed-off-by: David Wood <david.wood@huawei.com>
The two methods are almost identical.
By using `expr_str` more and adding `expr_{char,byte_str}`.
- Rename `ast::Lit::token` as `ast::Lit::token_lit`, because its type is `token::Lit`, which is not a token. (This has been confusing me for a long time.) reasonable because we have an `ast::token::Lit` inside an `ast::Lit`. - Rename `LitKind::{from,to}_lit_token` as `LitKind::{from,to}_token_lit`, to match the above change and `token::Lit`.
IEEE-754, not IEEE-745. May save someone a second sometime
Quick pull request; IEEE-754, not IEEE-745. May save someone a quick second some time.
…-test-cleanup, r=CraftSpider Rustdoc json tests: New @hasexact test command Alot of the time, we wanted to assert that a module had an exact set of items. Most of the time this was done by asserting that the ```@count``` of the module was `n`, and then doing `n` ```@has``` checks on the module. This was tedious, so often shortcuts were done. This PR adds a new command to jsondocck to allow consistently expressing this behavior, and then uses it to clean up the tests. ``@rustbot`` modify labels: +A-rustdoc-json +A-testsuite
interpret: only consider 1-ZST when searching for receiver `repr(transparent)` currently entirely rejects ZST with alignment larger than 1 (which is odd, arguably [this](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=02870f29396fa948c3123cb53d869ad1) should be accepted), so this should be safe. And if it ever isn't safe then that is very likely a bug elsewhere in the compiler.
…trochenkov Clean up `LitKind` r? ``@petrochenkov``
…imulacrum triagebot: add translation-related mention groups - Move some code around so that triagebot can ping relevant parties when translation logic is modified. - Add mention groups to triagebot for translation-related files/folders. - Auto-label pull requests with changes to translation-related files/folders with `A-translation`. r? `@Mark-Simulacrum`
…tion-cycle, r=cjgillot Do not report cycle error when inferring return type for suggestion The UI test is a good example of a case where this happens. The cycle is due to needing the value of the return type `-> _` to compute the variances of items in the crate, but then needing the variances of the items in the crate to do typechecking to infer what `-> _`'s real type is. Since we're already gonna emit an error in astconv, just delay the cycle bug as an error.
`is_knowable` use `Result` instead of `Option`
…acrum unwind: don't build dependency when building for Miri This is basically re-submitting rust-lang#94813. In that PR there was a suggestion to instead have bootstrap set a `RUST_CHECK` env var and use that rather than doing something Miri-specific. However, such an env var would mean that when switching between `./x.py check` and `./x.py build`, the build script gets re-run each time, which doesn't seem good. So I think for now checking for Miri probably causes fewer problems. r? ````@Mark-Simulacrum````
…KO8Ki needless separation of impl blocks
Pass +atomics-32 feature for {arm,thumb}v4t-none-eabi Similar to rust-lang@89582e8, but for ARMv4t. Pre-v6 ARM target does not have atomic CAS, except for Linux and Android where atomic CAS is provided by compiler-builtins. So, there is a similar issue as thumbv6m. I have confirmed that enabling the `atomics-32` target feature fixes the problem in the project affected by this issue. (taiki-e/portable-atomic#28 (comment)) Closes rust-lang#100619 r? ``@nikic`` cc ``@Lokathor``
⌛ Testing commit 1199dbd with merge 6146e596b71fc154320e6c37fb645f0fe85184b3... |
💥 Test timed out |
@bors retry |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (9c20b2a): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesThis benchmark run did not return any relevant results for this metric. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
Probably this one: @rust-timer build 8203583dca6e7de881b6615120538fea7be69577 |
Queued 8203583dca6e7de881b6615120538fea7be69577 with parent 86c6ebe, future comparison URL. |
Finished benchmarking commit (8203583dca6e7de881b6615120538fea7be69577): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
indeed, the regressing benchmarks for PR #100652 include the serde, unify-linearly and deep-vector cases that the rollup suffered from, all by similar amounts. (only ucd was absent from the narrower view). I tagged PR #100652 as a perf regression, and thus will mark this PR as triaged. @rustbot label: +perf-regression-triaged |
Successful merges:
LitKind
#100018 (Clean upLitKind
)is_knowable
useResult
instead ofOption
#100489 (is_knowable
useResult
instead ofOption
)SessionDiagnostic
in rustc_interface #100646 (Migrate emoji identifier diagnostics toSessionDiagnostic
in rustc_interface)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup