-
Notifications
You must be signed in to change notification settings - Fork 13.9k
Rollup of 8 pull requests #148390
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 8 pull requests #148390
Conversation
This updates the rust-version file to 402ce0e.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: 402ce0e Filtered ref: 33df85ebec1b1ac6085e256a69581e3d36cfd514 Upstream diff: rust-lang/rust@28d0a4a...402ce0e This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
This updates the rust-version file to 96fe3c3.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: 96fe3c3 Filtered ref: 376a7557c3e562036e170fb694d45d70b14951c3 Upstream diff: rust-lang/rust@402ce0e...96fe3c3 This merge was created using https://github.com/rust-lang/josh-sync.
native_call: we only support thin pointers as return type
This updates the rust-version file to 6244eff.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: 6244eff Filtered ref: 2b788f903ef58db43f16530dbf73f4a0502e4452 Upstream diff: rust-lang/rust@96fe3c3...6244eff This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
SB wildcard handling: extend comments
…cargo-toml Avoid panicking when `Cargo.toml` is not present
This updates the rust-version file to 27050c0.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: 27050c0 Filtered ref: 2bccf110c70c6f6ec349ede9fbf0b4cdcf77eac6 Upstream diff: rust-lang/rust@6244eff...27050c0 This merge was created using https://github.com/rust-lang/josh-sync.
Automatic Rustup
add -Zmiri-user-relevant-crates
add miri magic function to configure allocation tracking at runtime
This "cleanup" function is more than a decade old, and I can't find any evidence of modern-day bootstrap being able to pass any of these flags to `--host-rustcflags` or `--target-rustcflags`.
There are probably plenty of tests that will check this incidentally, but it's convenient to have a dedicated self-test.
In particular, this eliminates the cryptic `of: &TestPaths` parameters.
This method no longer returns a `TestPaths`, so the old name is no longer appropriate.
…e-func-calls Support `f32`/`f64` in native function calls
weak memory: fix non-atomic read clearing store buffer
split definition and use site hidden tys Tracking this implicitly is kinda messy and easy to get wrong. r? ``@BoxyUwU``
compiletest: Remove `cleanup_debug_info_options` This "cleanup" function is more than a decade old, and I can't find any evidence of modern-day bootstrap being able to pass any of these flags to `--host-rustcflags` or `--target-rustcflags`. I thought about replacing the cleanup with an assertion, but I think it's better to delete it entirely for now, and re-add checks later if they're motivated by actual problems in practice. In addition to deleting some old and confusing code, this also lets us remove three instances of duplicating `TestCx`, which is the biggest win. r? jieyouxu
compiletest: Don't modify `testpaths` when creating aux contexts Modifying `TestCx::testpaths` makes it vastly harder to reason about how compiletest is using test paths, and can be avoided without much trouble by simply passing explicit source-file paths into a small number of auxiliary-aware methods. --- This PR was originally based on a much larger change that split `TestPaths` into multiple structs and multiple `TestCx` fields (as seen in early revisions of rust-lang#148160), but after further cleanups it turned out that very few tweaks were actually needed to avoid changes to `testpaths`. r? jieyouxu
…ercote
Do not emit solver errors that contain error types
any follow-up errors are going to either be duplicates or often disappear if the error itself is fixed.
in this PR it mostly silences dyn-compat errors as all the other errors are already deduplicated outside of the test suite. The dyn compat errors are independent errors and I think if the dyn compatiblity depended on an error type it would not actually show, so this is PR is actually silencing independent errors, too.
I am opening this PR because I am seeing lots of `{type error}: const Trait` errors when adding more const checking. So instead of targetting just those specific errors, I wanted to try out fully avoiding such errors near the trait solver.
cc ````@rust-lang/types```` for thoughts
temporary-lifetime-extension.rs test works in all editions
…r=Noratrieb docs: makes a note about possible building `rustc 1.91.0 + host tools` for win7 I have make notes in docs that there is possible to build host tools for target `x86_64-win7-windows-msvc`. <img width="668" height="331" alt="image" src="https://github.com/user-attachments/assets/0335bc72-963c-4bfd-9910-61963dbf7dd7" /> r? ``````@roblabla`````` ``````@rustbot`````` label A-docs O-windows-7 P.S. prebuilt binaries can be found [here](https://github.com/Fenex/rust-win7/releases).
…ouxu Use --print host-tuple to get the host `--print host-tuple` has been available since 1.84 so there's no longer a need to parse the output of `-vV`. Especially since this script is shipped with the toolchain.
miri subtree update Subtree update of `miri` to rust-lang/miri@52c5daf. Created using https://github.com/rust-lang/josh-sync. r? `@ghost`
|
@bors r+ rollup=never p=5 |
|
☀️ Test successful - checks-actions |
|
📌 Perf builds for each rolled up PR:
previous master: 73e6c9ebd9 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 73e6c9e (parent) -> 6a884ad (this PR) Test differencesShow 112 test diffsStage 1
Stage 2
Additionally, 104 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 6a884ad1b502fe48307d363858510702429fc735 --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 (6a884ad): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 472.641s -> 474.95s (0.49%) |
Successful merges:
cleanup_debug_info_options#148194 (compiletest: Removecleanup_debug_info_options)testpathswhen creating aux contexts #148199 (compiletest: Don't modifytestpathswhen creating aux contexts)rustc 1.91.0 + host toolsfor win7 #148362 (docs: makes a note about possible buildingrustc 1.91.0 + host toolsfor win7)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup