miri ABI compatibility check: accept u32 and i32

[RalfJung]

If only the sign differs, then surely these types are compatible. (We do still check that arg_ext is the same, just in case.)

Also I made it so that the ABI check must imply that size and alignment are the same, but it doesn't actively check that itself. With how crazy ABI constraints get, having equal size and align really shouldn't be used as a signal for anything I think...

[rustbot]

r? @b-naber

(rustbot has picked a reviewer for you, use r? to override)

[rustbot]

Some changes occurred to the CTFE / Miri engine

cc @rust-lang/miri

The Miri subtree was changed

cc @rust-lang/miri

[b-naber]

@bors r+ rollup

[bors]

📌 Commit 5194060 has been approved by b-naber

It is now in the queue for this repository.

[bors]

⌛ Testing commit 5194060 with merge 191dc54...

[bors]

☀️ Test successful - checks-actions
Approved by: b-naber
Pushing 191dc54 to master...

[rust-timer]

Finished benchmarking commit (191dc54): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Warning ⚠: The following benchmark(s) failed to build:

• cargo-0.60.0

cc @rust-lang/wg-compiler-performance

Instruction count

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

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)	1.4%	[0.7%, 2.1%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Cycles

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

Binary size

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

Bootstrap: 631.054s -> 629.903s (-0.18%)
Artifact size: 316.21 MiB -> 316.24 MiB (0.01%)

[lqd]

The cargo benchmark timeout failure looks transient, and the next PR somehow had enough data to compute a diff on most of them 🤔