-
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 5 pull requests #97825
Rollup of 5 pull requests #97825
Conversation
… feature be enabled
Haiku doesn't define SIGIO. The nix crate already employs this workaround: https://github.com/nix-rust/nix/blob/5dedbc7850448ae3922ab0a833f3eb971bf7e25f/src/sys/signal.rs#L92-L94
This is a tiny optimization
It returns the previous work product or panics if there is none. This rename makes the purpose of this method clearer.
This improves clarity of the code a bit
A WorkProduct without a saved file is useless
Co-authored-by: Eduard-Mihai Burtescu <edy.burt@gmail.com>
I was experimenting with cross-language LTO for the wasm target recently between Rust and C and found that C was injecting the `+mutable-globals` flag on all functions. When specifying the corresponding `-Ctarget-feature=+mutable-globals` feature to Rust it prints a warning about an unknown feature. I've added the `mutable-globals` feature plus another few I know of to the list of known features for wasm targets. These features all continue to be unstable to source code as they were before.
…, r=nagisa Various refactors to the incr comp workproduct handling This is the result of me looking into adding support for having multiple object files for a single codegen unit to incr comp. This is necessary to support inline assembly in cg_clif without requiring partial linking which is not supported on Windows and seems to fail on macOS for some reason. Cg_clif uses an external assembler to handle inline asm and thus produces one object file with regular functions and one object file containing compiled inline asm for each codegen unit which uses inline asm. Current incr comp can't handle this. This PR doesn't yet add support for this, but it makes it easier to do so.
…rochenkov Allow unstable items to be re-exported unstably without requiring the feature be enabled Closes rust-lang#94972 The diagnostic may need some work still, and I haven't added a test yet
Fix ICEs from zsts within unsized types with non-zero offsets - Fixes rust-lang#97732 - Fixes ICEs while compiling `alloc` with `-Z randomize-layout` r? ``@eddyb``
Remove SIGIO reference on Haiku Haiku doesn't define SIGIO. The nix crate already employs this workaround: https://github.com/nix-rust/nix/blob/5dedbc7850448ae3922ab0a833f3eb971bf7e25f/src/sys/signal.rs#L92-L94
…chenkov Add some unstable target features for the wasm target codegen I was experimenting with cross-language LTO for the wasm target recently between Rust and C and found that C was injecting the `+mutable-globals` flag on all functions. When specifying the corresponding `-Ctarget-feature=+mutable-globals` feature to Rust it prints a warning about an unknown feature. I've added the `mutable-globals` feature plus another few I know of to the list of known features for wasm targets. These features all continue to be unstable to source code as they were before.
@bors r+ rollup=never p=5 |
📌 Commit 9526653 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (7fe2c4b): 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. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
stm32f4-0.14.0 regressed for check+debug+opt on Given that all the regressions are to incremental, I'm assuming this is because of #97058 |
Skimming over #97058, nothing stands out as being an obvious cause for a regression, even a small one. |
skimming over the perf details for stm32f4 check, it seems like the bulk of the time delta is coming from |
given the relatively small size and scope of the regression, and the fact that it was in a rollup, I do not think this is worth investigating further. @rustbot label: +perf-regression-triaged |
Rollup of 5 pull requests Successful merges: - rust-lang#97058 (Various refactors to the incr comp workproduct handling) - rust-lang#97301 (Allow unstable items to be re-exported unstably without requiring the feature be enabled) - rust-lang#97738 (Fix ICEs from zsts within unsized types with non-zero offsets) - rust-lang#97771 (Remove SIGIO reference on Haiku) - rust-lang#97808 (Add some unstable target features for the wasm target codegen) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Successful merges:
Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup