Skip to content

Rollup of 8 pull requests #120624

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 21 commits into from
Feb 4, 2024
Merged

Rollup of 8 pull requests #120624

merged 21 commits into from
Feb 4, 2024

Conversation

matthiaskrgr
Copy link
Member

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

Teapot4195 and others added 21 commits January 29, 2024 21:01
- Use `const_io_error` instead of `Error::new`
- Use the same message as `read_exact`
Update the library paths to correctly refer to libdemo{1,2}_hexagon
and switch to the release build instead.

Update references to libstandalone to the specific G0/PIC archive instead.
…piler-errors

Avoid ICE when is_val_statically_known is not of a supported type

2 ICE with 1 stone!
1. Implement `llvm.is.constant.ptr` to avoid first ICE in linked issue.
2. return `false` when the argument is not one of `i*`/`f*`/`ptr` to avoid second ICE.

fixes rust-lang#120480
…r-errors

pattern_analysis: cleanup manual impls

rust-lang#120420 introduced some unneeded manual impls. I remove them here.

r? ```@Nilstrieb```
… r=compiler-errors

never patterns: It is correct to lower `!` to `_`.

This is just a comment update but a non-trivial one: it is correct to lower `!` patterns as `_`. The reasoning is that `!` matches all the possible values of the type, since the type is empty. Moreover, we do want to warn that the `Err` is redundant in:
```rust
match x {
  !,
  Err(!),
}
```
which is consistent with `!` behaving like a wildcard.

I did try to introduce `Constructor::Never` and it ended up needing to behave exactly like `Constructor::Wildcard`.

r? ```@compiler-errors```
…he8472

Improve `io::Read::read_buf_exact` error case

- Use `const_io_error` instead of `Error::new`
- Use the same message as `read_exact`
…, r=cuviper

Store SHOULD_CAPTURE as AtomicU8

`BacktraceStyle` easily fits into a u8, so `SHOULD_CAPTURE`, which is just `Atomic<Option<BacktraceStyle>>`, should be stored as `AtomicU8`
…cuviper

Update data layouts in custom target tests for LLVM 18

Apply the data layout changes from rust-lang#116672 to custom target specs as well, as we started validating them since rust-lang#120062.

Fixes rust-lang#120492.

r? ```@cuviper```
Remove a bunch of `has_errors` checks that have no meaningful or the wrong effect

r? `@nnethercote`
…=wesleywiser

Correct paths for hexagon-unknown-none-elf platform doc

Update the library paths to correctly refer to libdemo{1,2}_hexagon and switch to the release build instead.

Update references to libstandalone to the specific G0/PIC archive instead.
@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Feb 3, 2024
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=108

@bors
Copy link
Collaborator

bors commented Feb 3, 2024

📌 Commit edd2494 has been approved by matthiaskrgr

It is now in the queue for this repository.

@bors
Copy link
Collaborator

bors commented Feb 3, 2024

🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 3, 2024
@bors
Copy link
Collaborator

bors commented Feb 4, 2024

⌛ Testing commit edd2494 with merge 268dbbb...

@bors
Copy link
Collaborator

bors commented Feb 4, 2024

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 268dbbb to master...

1 similar comment
@bors
Copy link
Collaborator

bors commented Feb 4, 2024

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 268dbbb to master...

@bors bors added merged-by-bors This PR was explicitly merged by bors. labels Feb 4, 2024
@bors bors merged commit 268dbbb into rust-lang:master Feb 4, 2024
@rustbot rustbot added this to the 1.78.0 milestone Feb 4, 2024
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#120484 Avoid ICE when is_val_statically_known is not of a supporte… 9d3161a20568abc36bf7aa40d0f5d0223cfbebb3 (link)
#120516 pattern_analysis: cleanup manual impls 7e49221d13ae436b53c81ed7a7209e545a69cd39 (link)
#120517 never patterns: It is correct to lower ! to _. c34e69ecff22ed6367b2bb8a5e7ab7eb0f803812 (link)
#120523 Improve io::Read::read_buf_exact error case 0aae44aed9ae87bc2b102c30387c23587d55c722 (link)
#120528 Store SHOULD_CAPTURE as AtomicU8 313bd9d01f17ff2da9632a16a964d41d162baad3 (link)
#120529 Update data layouts in custom target tests for LLVM 18 033e641cb534cb37d253a8b5fadd33f1458cf439 (link)
#120531 Remove a bunch of has_errors checks that have no meaningf… 10ea382b46ca289d4211220487f99a5e533dc297 (link)
#120533 Correct paths for hexagon-unknown-none-elf platform doc fcd463c49cf6e0428faf4bbf5ee0c96cadb44d7d (link)

previous master: 4e3eed4892

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (268dbbb): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
2.8% [2.8%, 2.8%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.8% [2.8%, 2.8%] 1

Max RSS (memory usage)

Results

This 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.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.8% [-2.2%, -1.4%] 2
Improvements ✅
(secondary)
-2.5% [-2.6%, -2.4%] 3
All ❌✅ (primary) -1.8% [-2.2%, -1.4%] 2

Cycles

Results

This 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.

mean range count
Regressions ❌
(primary)
2.4% [2.4%, 2.4%] 1
Regressions ❌
(secondary)
3.6% [3.6%, 3.6%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.4% [2.4%, 2.4%] 1

Binary size

Results

This 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.

mean range count
Regressions ❌
(primary)
0.1% [0.0%, 0.2%] 7
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.0% [-0.0%, -0.0%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.1% [-0.0%, 0.2%] 8

Bootstrap: 661.383s -> 661.592s (0.03%)
Artifact size: 308.07 MiB -> 308.07 MiB (-0.00%)

@matthiaskrgr matthiaskrgr deleted the rollup-3gvcl20 branch March 16, 2024 18:18
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.