summary refs log tree commit diff
path: root/compiler/rustc_mir/src/interpret/machine.rs
AgeCommit message (Collapse)AuthorLines
2020-12-11Fix rustfmt failureJCTyblaidd-1/+1
2020-12-11Add post-initialization hook for static memory initialized using the ↵JCTyblaidd-0/+10
interpereter.
2020-12-10Auto merge of #79621 - usbalbin:constier_maybe_uninit, r=RalfJungbors-1/+1
Constier maybe uninit I was playing around trying to make `[T; N]::zip()` in #79451 be `const fn`. One of the things I bumped into was `MaybeUninit::assume_init`. Is there any reason for the intrinsic `assert_inhabited<T>()` and therefore `MaybeUninit::assume_init` not being `const`? --- I have as best as I could tried to follow the instruction in [library/core/src/intrinsics.rs](https://github.com/rust-lang/rust/blob/master/library/core/src/intrinsics.rs#L11). I have no idea what I am doing but it seems to compile after some slight changes after the copy paste. Is this anywhere near how this should be done? Also any ideas for name of the feature gate? I guess `const_maybe_assume_init` is quite misleading since I have added some more methods. Should I add test? If so what should be tested?
2020-12-06Fix comments related to abort()Albin Hedman-4/+2
2020-12-05abort() now takes a msg parameterAlbin Hedman-2/+4
2020-12-03move interpret::MemoryKind::Heap to const evalVishnunarayan K I-4/+4
2020-10-13Replace absolute paths with relative onesest31-3/+4
Modern compilers allow reaching external crates like std or core via relative paths in modules outside of lib.rs and main.rs.
2020-08-30mv compiler to compiler/mark-0/+422