-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 9 pull requests #120112
Rollup of 9 pull requests #120112
Conversation
…rors up instead.
addres -> address
Signed-off-by: onur-ozkan <[email protected]>
…esleywiser bootstrap: handle vendored sources when remapping crate paths rust-lang#115872 introduced a feature to add path remapping for crate dependencies, but only when they came from Cargo's registry cache, not a vendor directory. This caused builds that used remapped debuginfo and vendor directories to fail with: ``` std::fs::read_dir(registry_src) failed with No such file or directory (os error 2) ``` or (if the `registry/src` directory exists but is empty) ``` error: --remap-path-prefix must contain '=' between FROM and TO ``` Fixes rust-lang#117885 by explicitly supporting the `vendor` directory and adding it to `RUSTC_CARGO_REGISTRY_SRC_TO_REMAP`. Note that `bootstrap.py` already assumes that `./vendor` within the rust repo is the only supported vendoring location. r? `@pietroalbini`
docs: fix typos
…_improved_attr, r=petrochenkov Improved collapse_debuginfo attribute, added command-line flag Improved attribute collapse_debuginfo with variants: `#[collapse_debuginfo=(no|external|yes)]`. Added command-line flag for default behaviour. Work-in-progress: will add more tests. cc rust-lang#100758
…sper replace `track_errors` usages with bubbling up `ErrorGuaranteed` more of the same as rust-lang#117449 (removing `track_errors`)
…ar-helper, r=lcnr Remove `next_root_ty_var` Uhh we seem to not have any test that relies on this anymore. Maybe due to the way we changed alias-relate or whatever. Removing this hack helper fn because rust-lang#119106 is the general solution. r? lcnr
…ikic tests/ui/asm/inline-syntax: adapt for LLVM 18 Fixes rust-lang#119120.
Set RUSTC_BOOTSTRAP=1 consistently Fixes https://internals.rust-lang.org/t/rust-compiler-with-parallel-build/20099 which is a regression from rust-lang#120001 cc `@dtolnay` `@petrochenkov`
…Lapkin change `.unwrap()` to `?` on write where `fmt::Result` is returned Fixes rust-lang#120090 which points out that some of the `.unwrap()`s in `rustc_middle/src/mir/pretty.rs` are likely meant to be `?`s
Fix typo in munmap_partial.rs addres -> address
@bors r+ rollup=never p=9 |
💥 Test timed out |
@bors retry |
@bors p=11 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 16fadb3f25 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (92d7277): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 663.017s -> 665.984s (0.45%) |
Type checking seems to have regressed. Maybe #119869 or #120037? Let's see. @rust-timer build 9e918d1 |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (9e918d1): comparison URL. Overall result: no relevant changes - no action neededInstruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 663.017s -> 663.908s (0.13%) |
No, that was not it. @rust-timer build d62113d |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (d62113d): comparison URL. Overall result: ❌ regressions - ACTION NEEDEDInstruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 663.017s -> 665.959s (0.44%) |
That seems to be it. @compiler-errors was the regression expected? |
No, but looking back at the rollup (for the PR #112399) that added the helper function that I removed, it seems to have just undone the perf win here: So I think we can just ignore this perf regression. |
Ok. @rustbot label: +perf-regression-triaged |
Successful merges:
track_errors
usages with bubbling upErrorGuaranteed
#119869 (replacetrack_errors
usages with bubbling upErrorGuaranteed
)next_root_ty_var
#120037 (Removenext_root_ty_var
).unwrap()
to?
on write wherefmt::Result
is returned #120101 (change.unwrap()
to?
on write wherefmt::Result
is returned)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup