Rollup of 8 pull requests

[matthiaskrgr]

Successful merges:

• Remove arena_cache modifier from upstream_monomorphizations_for #107719 (Remove arena_cache modifier from upstream_monomorphizations_for)
• Avoid locking the global context across the after_expansion callback #107740 (Avoid locking the global context across the after_expansion callback)
• Split fn_ctxt/adjust_fulfillment_errors from fn_ctxt/checks #107746 (Split fn_ctxt/adjust_fulfillment_errors from fn_ctxt/checks)
• allow quick-edit convenience #107749 (allow quick-edit convenience)
• make more readable #107750 (make more readable)
• remove binder from query constraints #107755 (remove binder from query constraints)
• miri: fix ICE when running out of address space #107756 (miri: fix ICE when running out of address space)
• llvm-16: Use Triple.h from new header location. #107764 (llvm-16: Use Triple.h from new header location.)

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[matthiaskrgr]

@bors r+ rollup=never p=8

[bors]

📌 Commit 232213d has been approved by matthiaskrgr

It is now in the queue for this repository.

[bors]

⌛ Testing commit 232213d with merge 3f059f6...

[bors]

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 3f059f6 to master...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Perf Build Sha
#107764	50c21a84c6bfcbfd3980b6b8091bf2fc452e6360
#107756	b7ba6111317121b7e746bf2d80ff928454ff977d
#107755	714f77261ee2f3c80f0c9903939ace84cf060fc4
#107750	eed5f9aea547b88e9d31c4ce354c2c4f5baf8d99
#107749	321aa22d2e44796152fd683778e14cbee7fafb10
#107746	b9641bc999f66e9f6ae356928dfcb5438c6d0905
#107740	8a431d0da68087275ca528ca5eb8cba61b522d5a
#107719	e3691ec17fad154ff5ef578c5fadcfea71fa8344

previous master: bd39bbb4bb

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]

Finished benchmarking commit (3f059f6): comparison URL.

Overall result: ❌✅ regressions and improvements - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

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)	-	-	0
Regressions ❌ (secondary)	1.7%	[1.7%, 1.7%]	2
Improvements ✅ (primary)	-1.0%	[-1.5%, -0.4%]	3
Improvements ✅ (secondary)	-3.7%	[-4.2%, -3.2%]	6
All ❌✅ (primary)	-1.0%	[-1.5%, -0.4%]	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.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.7%	[2.2%, 3.2%]	2
Improvements ✅ (primary)	-1.8%	[-3.9%, -0.6%]	3
Improvements ✅ (secondary)	-4.3%	[-4.3%, -4.3%]	1
All ❌✅ (primary)	-1.8%	[-3.9%, -0.6%]	3

Cycles

This benchmark run did not return any relevant results for this metric.

[rylev]

Small number of regressions in secondary benchmarks in a rollup - I think we're fine calling this triaged.

@rustbot label: perf-regression-triaged