Repository navigation
Rollup of 7 pull requests - #165617
Rollup of 7 pull requests#165617
Conversation
This removes the need for workarounds to ensure drops are run (e.g. for `TempDir` cleanup).
It will ensure library options are picked up by new contexts, and lets us handle errors explicitly.
…nikic Parse LLVM options into an explicit global LibraryOptionsContext LLVM has been refactoring how it stores its internal (-mllvm) options recently, with the goal of getting rid of the global cl::opt objects. After http://github.com/llvm/llvm-project/pull/233044 LTO passes no longer uses the global options, which would cause codegen-llvm/pgo-counter-bias.rs to fail since it relies on the -runtime-counter-relocation option to get passed to LTO. Use the C API function LLVMParseCommandLineOptionsWithError which ensures the parsed options are picked up by new LLVMContexts.
Remove typed allocas and geps from `gpu_offload.rs` Typed GEPs are being removed from the rest of the compiler in rust-lang#165146, and typed allocas were already removed, so change `gpu_offload.rs` to match. This PR also removes the constant zero GEPs ([#t-compiler > GEP constant 0 in &rust-lang#96;gpu_offload.rs&rust-lang#96;](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/GEP.20constant.200.20in.20.60gpu_offload.2Ers.60/with/635158185)). r? @ZuseZ4
…=lolbinarycat rustdoc: remove `process::exit` This removes the need for workarounds to ensure drops are run (e.g. for `TempDir` cleanup) and hopefully prevents such situations from arising again.
update Enzyme submodule
…hanna-kruppe MIR opts: dont let optimize(size/none) increase the MIR opt level It does not seem right that with `-Zmir-opt-level=0`, an `optimize(none)` function gets optimized *more* than all the other functions.
coretests: speed up some tests in Miri
…nsts, r=JonathanBrouwer Replace the name of a removed MIR pass used in a test The `ConstDebugInfo` MIR pass was replaced by the `SingleUseConsts` pass in rust-lang#125910.
|
@bors r+ p=5 force |
|
The job Click to see the possible cause of the failure (guessed by this bot)Important For more information how to resolve CI failures of this job, visit this link. |
This comment has been minimized.
This comment has been minimized.
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 f5cedb8 (parent) -> 29f2825 (this PR) Test differencesShow 12 test diffsStage 1
Stage 2
Additionally, 2 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 29f282561639932ad8c56c11ef6313ffbc9bdb05 --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 (29f2825): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (secondary 1.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis perf run didn't have relevant results for this metric. Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 482.59s -> 482.346s (-0.05%) |
|
📌 Perf builds for each rolled up PR:
parent commit: f5cedb83a7 In the case of a perf regression, run the following command with the SHAs of each PR you suspect might be the cause: |
Successful merges:
gpu_offload.rs#165154 (Remove typed allocas and geps fromgpu_offload.rs)process::exit#165554 (rustdoc: removeprocess::exit)Failed merges:
r? @ghost
Create a similar rollup