Rollup of 8 pull requests#158068
Merged
Merged
Conversation
The current Linux driver treats every sendmsg call as a separate record. That is, it behaves as though MSG_EOR is always set. But that might not be true forever. And the current FreeBSD driver does _not_ do that, so setting MSG_EOR is important for portability.
…ameters in by-value returns" This reverts commit 519a555. The regression test added by that commit asserts that redundant stores are present, which locks in suboptimal assembly output and will actively block any future fix from landing.
Clarified how `with_added_extension` deals with the return value from `add_extension`. I added some "interesting" examples to illustrate.
This makes it consistent with the other late internal lints. It doesn't need to be a crate-level pass because it doesn't implement `check_crate` or `check_crate_post` and/or track any crate-level information.
Instead of N separate passes. This is more efficient for bootstrapping. It also matches what is done for builtin lints (`BuiltinCombined*LintPass`).
@abrown has [commented](rust-lang#157644 (comment)) that he is no longer maintaining the target. Update the target maintainers list accordingly.
Put internal lints into a single combined pass Details in individual commits. r? @Urgau
Take care to use MSG_EOR with SOCK_SEQPACKET sockets The current Linux driver treats every sendmsg call as a separate record. That is, it behaves as though MSG_EOR is always set. But that might not be true forever. And the current FreeBSD driver does _not_ do that, so setting MSG_EOR is important for portability. r? @the8472
wasm32-wasip1-threads: Correct llvm target name Intends to fix rust-lang#131007, a problem with cross-compiling Rust+C++ to wasm32-wasip1-threads: clang will be told to compile for `--target=wasm32-wasi`, which it interprets as `wasm32-wasip1`, which is not compatible with `wasm32-wasip1-threads`. I wonder if there might be any compatibility issue or something depending on the old incorrect name...
stabilize str_from_utf16_endian Closes rust-lang#116258
…vooeo Revert "add regression test for Redundant memory strores with mut parameters in by-value returns" This reverts commit 519a555 (PR rust-lang#154841). The regression test added by that commit asserts that redundant stores are present, which locks in suboptimal assembly output and will actively block any future fix from landing. The underlying issue (rust-lang#149762) is therefore not fixed. Since 1.92.0, both `with_rebind` and `with_mut_param` compile to the same suboptimal assembly, whereas in 1.91.0 `with_rebind` at least produced optimal output. A correct regression test should verify that neither function emits redundant stores, and should be added together with an actual fix. rust-lang#149762 (comment)
Document `with_added_extension` edge cases Clarified how `with_added_extension` deals with the return value from `add_extension`. I added some "interesting" examples to illustrate. IMO this function should have returned `Result` but unfortunately the discussion about that was kind of ignored. :-/ We can at least document it well. No AI was used to make this change.
…rs, r=JonathanBrouwer fix unresolved import suggestion before outer attributes Fixes rust-lang#69733. Issue rust-lang#69733 reports an invalid import suggestion where rustc could insert a new `use ...;` item between an outer attribute and the item it annotates. This invalid import suggestion produces broken code. My PR adds a `run-rustfix` UI regression test for that. The fixed output verifies that the suggested import is inserted before the leading outer attribute
rustc book: Update wasm32-wasip1-threads's maintainers list @abrown has [commented](rust-lang#157644 (comment)) that he is no longer maintaining the target. Update the target maintainers list accordingly. r? abrown
rustbot
added
S-waiting-on-review
Member
Author
|
@bors r+ rollup=never p=5 |
Contributor
rust-bors
Bot
added
S-waiting-on-bors
This comment has been minimized.
This comment has been minimized.
rust-bors
Bot
added
merged-by-bors
Contributor
Collaborator
|
📌 Perf builds for each rolled up PR:
previous master: 9639eefc07 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Contributor
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 9639eef (parent) -> c55fad5 (this PR) Test differencesShow 341 test diffsStage 1
Stage 2
Additionally, 336 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 c55fad5a9048ad0f7cff2a4867a297647af9392b --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 |
Merged
Collaborator
|
Finished benchmarking commit (c55fad5): 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 (primary 4.1%, secondary 2.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 3.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.0%, secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 482.613s -> 481.592s (-0.21%) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Successful merges:
with_added_extensionedge cases #158051 (Documentwith_added_extensionedge cases)r? @ghost
Create a similar rollup