rust/compiler/rustc_const_eval/src/interpret/place.rs, branch 1.86.0

miri: optimize zeroed alloc

2025-01-28T11:50:02+00:00

Co-authored-by: Ralf Jung

Avoid naming variables `str`

2025-01-07T12:30:02+00:00

This renames variables named `str` to other names, to make sure `str` always refers to a type. It's confusing to read code where `str` (or another standard type name) is used as an identifier. It also produces misleading syntax highlighting.

swap_typed_nonoverlapping: properly detect overlap even when swapping scalar values

2024-12-25T15:01:26+00:00

interpret: clean up deduplicating allocation functions

2024-12-09T14:12:33+00:00

Add allocate_bytes and refactor allocate_str in InterpCx for raw byte allocation

2024-12-07T11:06:17+00:00

Signed-off-by: shamb0

`InterpCx` store `TypingEnv` instead of a `ParamEnv`

2024-11-19T20:36:23+00:00

use `TypingEnv` when no `infcx` is available

2024-11-18T09:38:56+00:00

the behavior of the type system not only depends on the current assumptions, but also the currentnphase of the compiler. This is mostly necessary as we need to decide whether and how to reveal opaque types. We track this via the `TypingMode`.

stop using `ParamEnv::reveal` while handling MIR

2024-10-31T13:55:53+00:00

compiler: `rustc_abi::Abi` => `BackendRepr`

2024-10-29T21:56:00+00:00

The initial naming of "Abi" was an awful mistake, conveying wrong ideas about how psABIs worked and even more about what the enum meant. It was only meant to represent the way the value would be described to a codegen backend as it was lowered to that intermediate representation. It was never meant to mean anything about the actual psABI handling! The conflation is because LLVM typically will associate a certain form with a certain ABI, but even that does not hold when the special cases that actually exist arise, plus the IR annotations that modify the ABI. Reframe `rustc_abi::Abi` as the `BackendRepr` of the type, and rename `BackendRepr::Aggregate` as `BackendRepr::Memory`. Unfortunately, due to the persistent misunderstandings, this too is now incorrect: - Scattered ABI-relevant code is entangled with BackendRepr - We do not always pre-compute a correct BackendRepr that reflects how we "actually" want this value to be handled, so we leave the backend interface to also inject various special-cases here - In some cases `BackendRepr::Memory` is a "real" aggregate, but in others it is in fact using memory, and in some cases it is a scalar! Our rustc-to-backend lowering code handles this sort of thing right now. That will eventually be addressed by lifting duplicated lowering code to either rustc_codegen_ssa or rustc_target as appropriate.

interpret: Immediate::offset: use shared sanity-check function to ensure invariant

2024-10-03T06:26:25+00:00