diff options
| author | bors <bors@rust-lang.org> | 2023-07-21 16:32:44 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-07-21 16:32:44 +0000 |
| commit | c0de313e82a496285a8de1d4f01b579734b84c13 (patch) | |
| tree | 4699ba29309eeaac4df07655230738bbf3582232 /compiler/rustc_errors/src | |
| parent | e643e0d29f16c8cdd114c3c6e073b131c4e6d5bf (diff) | |
| parent | 3cdd2922cb828dee30bacdbed9f0a37602200e18 (diff) | |
| download | rust-c0de313e82a496285a8de1d4f01b579734b84c13.tar.gz rust-c0de313e82a496285a8de1d4f01b579734b84c13.zip | |
Auto merge of #2985 - RalfJung:retag-fields, r=saethlin
make full field retagging the default The 'scalar' field retagging mode is clearly a hack -- it mirrors details of the codegen backend and how various structs are represented in LLVM. This means whether code has UB or not depends on surprising aspects, such as whether a struct has 2 or 3 (non-zero-sized) fields. Now that both hashbrown and scopeguard have released fixes to be compatible with field retagging, I think it is time to enable full field retagging by default. `@saethlin` do you have an idea of how much fallout enabling full field retagging by default will cause? Do you have objections to enabling it by default? Fixes https://github.com/rust-lang/miri/issues/2528
Diffstat (limited to 'compiler/rustc_errors/src')
0 files changed, 0 insertions, 0 deletions