-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 7 pull requests #124040
Rollup of 7 pull requests #124040
Conversation
note: version more recent than 1.8 depend on memchr 2.6, which creates conflicts as memchr 2.5.0 is pinned elsewhere in the workspace
also check that turning off the linker feature does not use lld
also make sure that rust-lld can be disabled via linker features, even when enabled by default by the target spec
and use it in the `rust-lld` tests
If you want to override an env var, don't unset it, just set it
These types are always generic only over their own generic parameters with no inference variables involved.
To the best of my ability I believe that this is no longer necessary. I don't fully recall why this was first added but I believe it had to do with symbols all being exported by default and this was required to undo that. Regardless nowadays the default output of rustc seems suitable so it seems best to keep wasm in line with other targets.
…u,estebank Don't ICE for kind mismatches during error rendering fixes rust-lang#123457 also some test suite cleanups to make backtraces easier to read
…errors Taint const qualifs if a static is referenced that didn't pass wfcheck It is correct to only check the signature here, as the ICE is caused by `USE_WITH_ERROR` trying to allocate memory to store the result of `WITH_ERROR` before evaluating it. fixes rust-lang#123153
Port the 2 `rust-lld` run-make tests to `rmake` In preparation for finalizing most of the `rust-lld` work, this PR ports the following tests to `rmake`: - `tests/run-make/rust-lld` - `tests/run-make/rust-lld-custom-target` As they use `$(CGREP) -e` I added `regex` as an exported dependency to the `run_make_support` library. Unfortunately, the most recent versions depend on `memchr` 2.6.0 but it's currently pinned at 2.5.0 in the workspace, and therefore had to settle for the older `regex-1.8.0`. r? `@jieyouxu`
…leywiser Use `/* value */` as a placeholder The expression `value` isn't a valid suggestion; let's use `/* value */` as a placeholder (which is also invalid) since it more clearly signals to the user that they need to fill it in with something meaningful. This parallels the suggestions we have in a couple other places, like arguments. We could also print the type name instead of `/* value */`, especially if it's suggestable, but I don't care strongly about that.
Box::into_raw: make Miri understand that this is a box-to-raw cast Turns out rust-lang#122647 went a bit too far in cleaning up `Box`... we still need a hack in `Box::into_raw`. The nicer fix would be to make Stacked Borrows not care about reference-to-raw-pointer casts, but it's unclear whether that will ever be possible without going to full Tree Borrows. Fixes rust-lang/miri#3473.
…mpiler-errors Prefer identity equality over equating types during coercion. These types are always generic only over their own generic parameters with no inference variables involved. r? `@compiler-errors` I love touching code that [hasn't changed meaningfully since 2016](rust-lang#41937)
…ility, r=jieyouxu Remove `default_hidden_visibility: false` from wasm targets To the best of my ability I believe that this is no longer necessary. I don't fully recall why this was first added but I believe it had to do with symbols all being exported by default and this was required to undo that. Regardless nowadays the default output of rustc seems suitable so it seems best to keep wasm in line with other targets.
Could not assign reviewer from: |
@GuillaumeGomez: no appropriate reviewer found, use |
@bors r+ p=5 rollup=never |
testing triagebot r? ghost |
Failed to set assignee to
|
again r? @ghost |
Failed to set assignee to
|
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 3fba278231 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (7e3ba5b): 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)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 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: 676.389s -> 677.09s (0.10%) |
Successful merges:
rust-lld
run-make tests tormake
#123975 (Port the 2rust-lld
run-make tests tormake
)/* value */
as a placeholder #124000 (Use/* value */
as a placeholder)default_hidden_visibility: false
from wasm targets #124036 (Removedefault_hidden_visibility: false
from wasm targets)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup