diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2025-07-22 00:54:30 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-22 00:54:30 +0800 |
| commit | 9e9399fcf885e2d15cbb2157459802f365428aaa (patch) | |
| tree | 237866eb5d8f33fb7e4202a8f91f0ca4d43c921a /compiler/rustc_span | |
| parent | 0fd009ffe459bd121629c893446525eff6f1c8fe (diff) | |
| parent | 3f9be406a6fd879a99a0eba33cc196fa2cb3957b (diff) | |
| download | rust-9e9399fcf885e2d15cbb2157459802f365428aaa.tar.gz rust-9e9399fcf885e2d15cbb2157459802f365428aaa.zip | |
Rollup merge of #144187 - RalfJung:type-id-base-addr, r=oli-obk
fix handling of base address for TypeId allocations This fixes the problems discovered by ````@theemathas```` in https://github.com/rust-lang/rust/pull/142789: - const-eval would sometimes consider TypeId pointers to be null - the type ID is different in Miri than in regular executions Both boil down to the same issue: the TypeId "allocation" has a guaranteed 0 base address, but const-eval assumes it was non-zero (like normal allocations) and Miri randomized it (like normal allocations). r? ````@oli-obk````
Diffstat (limited to 'compiler/rustc_span')
0 files changed, 0 insertions, 0 deletions