Note that even ConstProp follows the rules
Co-authored-by: Ralf Jung <post@ralfj.de>
This commit is contained in:
parent
4c934df45f
commit
12a8d106f6
1 changed files with 2 additions and 2 deletions
|
@ -130,8 +130,8 @@ impl<Tag> Allocation<Tag> {
|
||||||
// This results in an error that can happen non-deterministically, since the memory
|
// This results in an error that can happen non-deterministically, since the memory
|
||||||
// available to the compiler can change between runs. Normally queries are always
|
// available to the compiler can change between runs. Normally queries are always
|
||||||
// deterministic. However, we can be non-determinstic here because all uses of const
|
// deterministic. However, we can be non-determinstic here because all uses of const
|
||||||
// evaluation will make compilation fail (via hard error or ICE) upon
|
// evaluation (including ConstProp!) will make compilation fail (via hard error
|
||||||
// encountering a `MemoryExhausted` error.
|
// or ICE) upon encountering a `MemoryExhausted` error.
|
||||||
InterpError::ResourceExhaustion(ResourceExhaustionInfo::MemoryExhausted)
|
InterpError::ResourceExhaustion(ResourceExhaustionInfo::MemoryExhausted)
|
||||||
})?;
|
})?;
|
||||||
bytes.resize(size.bytes_usize(), 0);
|
bytes.resize(size.bytes_usize(), 0);
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue