Skip to content

Rollup of 8 pull requests - #108677

Merged
bors merged 27 commits into
rust-lang:masterfrom
matthiaskrgr:rollup-i91cxuf
Mar 3, 2023
Merged

Rollup of 8 pull requests#108677
bors merged 27 commits into
rust-lang:masterfrom
matthiaskrgr:rollup-i91cxuf

Conversation

@matthiaskrgr

@matthiaskrgrmatthiaskrgr commented Mar 2, 2023

Copy link
Copy Markdown
Member

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

CraftSpiderand others added 27 commits February 20, 2023 13:47
…ons for miri. Credit to emarteca for the code.
This makes its `Debug` impl print it first which is useful, as it's the
most important part when looking at an expr.
Support allocations with non-Box<[u8]> bytes
This is prep work for allowing miri to support passing pointers to C code, which will require `Allocation`s to be correctly aligned. Currently, it just makes `Allocation` generic and plumbs the necessary changes through the right places.
The follow-up to this will be adding a type in the miri interpreter which correctly aligns the bytes, using that for the Miri engine, then allowing Miri to pass pointers into these allocations to C calls.
Based off of rust-lang#100467, credit to ```@emarteca``` for the code
… r=pietroalbini
Re-apply "switch to the macos-12-xl builder"
This reverts commit e63ec2e, essentially re-applying fcbae98.
r? ````@pietroalbini````
…-span-fix-Some, r=WaffleLapkin
Point error span at Some constructor argument when trait resolution fails
This is a follow up to rust-lang#108254 and rust-lang#106477 which extends error span refinement to handle a case which I mistakenly believed was handled in rust-lang#106477. The goal is to refine the error span depicted below:
```rs
trait Fancy {}
impl <T> Fancy for Option<T> where T: Iterator {}
fn want_fancy<F>(f: F) where F: Fancy {}
fn example() {
want_fancy(Some(5));
// (BEFORE) ^^^^^^^ `{integer}` is not an iterator
// (AFTER) ^ `{integer}` is not an iterator
}
```
I had used a (slightly more complex) example as an illustrative example in rust-lang#108254 , but hadn't actually turned it into a test, because I had (incorrectly) believed at the time it was covered by existing behavior. It turns out that `Some` is slightly "special" in that it resolves differently from the other `enum` constructors I had tried, and therefore this test was actually broken.
I've now updated the tests to include this example, and fixed the code to correctly resolve the `Some` constructor so that the span of the error is reduced.
Explain compile-time vs run-time difference in env!() error message
This PR is clarifying error message of `env!()` based on this user question: https://users.rust-lang.org/t/environment-variable-out-dir-is-undefined/90067
It makes it clear that `env!()` is for env variables defined at compile-time. There's special-case help text for common Cargo build script variables.
I've also rearranged the code to avoid allocating error message on the happy path when the env var is defined.
Make `ExprKind` the first field in `thir::Expr`
This makes its `Debug` impl print it first which is useful, as it's the most important part when looking at an expr.
…arsan68
Allow setting hashmap toml values in `./configure`
Fixesrust-lang#108621
…=compiler-errors
Feed queries on impl side for RPITITs when using lower_impl_trait_in_trait_to_assoc_ty
I've added a test for traits that were already working and what I think is probably the last bit of infrastructure work needed.
In following PRs I'm going to start adding things TDD style, tests and code that make it work.
r? `@compiler-errors`
@rustbotrustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Mar 2, 2023
@matthiaskrgr

Copy link
Copy Markdown
MemberAuthor

@bors treeclosed=100 aarch64 is not responding after github outage

@matthiaskrgr

Copy link
Copy Markdown
MemberAuthor

@bors retry p=142

@bors

bors commented Mar 3, 2023

Copy link
Copy Markdown
Collaborator

⌛ Testing commit e85df8d with merge 7a809ce...

@matthiaskrgr

Copy link
Copy Markdown
MemberAuthor

@bors treeclosed-

@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

A job failed! Check out the build log: (web)(plain)

Click to see the possible cause of the failure (guessed by this bot)

@bors

bors commented Mar 3, 2023

Copy link
Copy Markdown
Collaborator

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 7a809ce to master...

@borsbors added the merged-by-bors This PR was explicitly merged by bors. label Mar 3, 2023
@bors
bors merged commit 7a809ce into rust-lang:masterMar 3, 2023
@rustbotrustbot added this to the 1.69.0 milestone Mar 3, 2023
@rust-timer

Copy link
Copy Markdown
Collaborator

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (7a809ce): comparison URL.

Overall result: ✅ improvements - 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.

meanrangecount
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
--0
Improvements ✅
(primary)
-0.6%[-0.7%, -0.6%]3
Improvements ✅
(secondary)
-0.4%[-0.5%, -0.3%]4
All ❌✅ (primary)-0.6%[-0.7%, -0.6%]3

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.

meanrangecount
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
2.1%[1.7%, 2.5%]2
Improvements ✅
(primary)
-2.1%[-2.1%, -2.1%]1
Improvements ✅
(secondary)
-3.4%[-3.4%, -3.4%]1
All ❌✅ (primary)-2.1%[-2.1%, -2.1%]1

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.

meanrangecount
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
--0
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
-2.1%[-2.1%, -2.1%]1
All ❌✅ (primary)--0

@matthiaskrgr
matthiaskrgr deleted the rollup-i91cxuf branch March 16, 2024 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-testsuiteArea: The testsuite used to check the correctness of rustcmerged-by-borsThis PR was explicitly merged by bors.rollupA PR which is a rollupS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

14 participants

@matthiaskrgr@bors@ehuss@rust-log-analyzer@rust-timer@rustbot@CraftSpider@compiler-errors@Nathan-Fenner@kornelski@GuillaumeGomez@KittyBorgX@Noratrieb@spastorino