Conversation
I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.
…mulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.
…plit, r=Amanieu split up tracking issue for target feature feature gates rust-lang#44839 is tracking too many things at once. We usually have a separate tracking issue for each feature gate, so let's do that here as well: - rust-lang#150244 - rust-lang#150245 - rust-lang#150246 - rust-lang#150247 - rust-lang#150248 - rust-lang#150249 - rust-lang#150250 - rust-lang#150251 - rust-lang#150252 - rust-lang#150253 - rust-lang#150254 - rust-lang#150255 - rust-lang#150256 - rust-lang#150257 - rust-lang#150258 - rust-lang#150259 - rust-lang#150260 - rust-lang#150261 Closes rust-lang#44839 in favor of the ones listed above. r? `@Amanieu`
…ewrite, r=BoxyUwU `region_scope_tree`: Rewrite a `loop` as tail recursion This addresses rust-lang#146098 (comment), hopefully making `record_subexpr_extended_temp_scopes` a bit more legible. I removed a `debug!` in the process, since the function it calls every iteration, [`ScopeTree::record_extended_temp_scope`](https://github.com/rust-lang/rust/blob/2848c2ebe9a8a604cd63455263299d7258bc8252/compiler/rustc_middle/src/middle/region.rs#L264-L271), does the same `debug!`. Keeping the behavior of having an additional `debug!` for the top-level expression would hurt legibility, and having a duplicate `debug!` at each iteration seems excessive. No information is lost from the debug output, so I think it's fine to just have the inner `debug!`s. r? BoxyUwU or anyone
…=chenyukang Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets This flag enables the `#[instruction_set(arm::t32)]` for the armv7a/armv7r/armv8r targets, which all support Thumb interwork but were missing this flag. Target maintainers are `@chrisnc,` `@rust-lang/arm-maintainers,` `@rust-embedded/arm` (including me).
|
@bors r+ rollup=never p=5 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: 4c62aa4468 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 4c62aa4 (parent) -> 6e48b44 (this PR) Test differencesShow 36 test diffs36 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 6e48b44e77d117d84ff3c340368dea3064117559 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (6e48b44): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 2.5%, secondary -3.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 9.2%, secondary 16.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 476.46s -> 476.234s (-0.05%) |
Successful merges:
crate::io::Result→io::Resultin most places #149778 (crate::io::Result→io::Resultin most places)region_scope_tree: Rewrite aloopas tail recursion #150548 (region_scope_tree: Rewrite aloopas tail recursion)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup