Add MemoryExtra in InterpretCx constructor params#62158
Add MemoryExtra in InterpretCx constructor params#62158bors merged 3 commits intorust-lang:masterfrom pvdrz:ecx-memory-extra
Conversation
|
Please also change |
I believe this is still required for all the Edit: Here for example: https://github.com/rust-lang/rust/blob/0a7b9953672e1c5cedee029b288fdc1d7b794cc7/src/librustc_mir/const_eval.rs#L50 |
|
That code will still work fine because there we are using a concrete But what the trait says is that anyone implementing the |
|
It would be @bors r+ |
|
📌 Commit 74a9c6eefcfa6469fae9f76d023429c0cb619ead has been approved by |
|
🌲 The tree is currently closed for pull requests below priority 999, this pull request will be tested once the tree is reopened |
|
💡 This pull request was already approved, no need to approve it again.
|
|
📌 Commit 74a9c6eefcfa6469fae9f76d023429c0cb619ead has been approved by |
|
🌲 The tree is currently closed for pull requests below priority 999, this pull request will be tested once the tree is reopened |
|
💡 This pull request was already approved, no need to approve it again.
|
|
📌 Commit 74a9c6eefcfa6469fae9f76d023429c0cb619ead has been approved by |
|
🌲 The tree is currently closed for pull requests below priority 999, this pull request will be tested once the tree is reopened |
Oh ok! Thank you! |
|
@christianpoveda: 🔑 Insufficient privileges: Not in reviewers |
|
@bors rollup=never (breaks Miri) @rust-lang/infra why does |
|
Remember that rust-lang/miri#792 needs these changes to work |
|
I do. The thing is, we are about to branch off beta in less than a week, which means changes that break Miri cannot land. So once #62105 lands, we'll have to fold a Miri update into this PR. |
|
Looks very much like the Miri update will land first, so let's avoid wasting CI time. @bors r- |
|
@christianpoveda okay the Miri PR landed, are you ready to update this one? I prepared the |
|
Now how do I get rid of this "rollup=never" thing... @bors rollup- |
|
☔ The latest upstream changes (presumably #62253) made this pull request unmergeable. Please resolve the merge conflicts. |
|
@christianpoveda we got overtaken by another PR that also modifies Miri... can you do a rebase and do the submodule update again? I updated the |
|
Alternatively, you can remove the miri-updating commit and we wait until Wednesday, when we get out of the "freeze" for tools. |
I will do this, it seems the better option right now |
|
It's just 4h until it's Wednesday UTC, I feel confident this will not land fast enough to cause problems and I want to stop having to remember.^^ @bors r+ |
|
📌 Commit e32b8eb has been approved by |
|
☔ The latest upstream changes (presumably #62355) made this pull request unmergeable. Please resolve the merge conflicts. |
|
@bors r+ |
|
📌 Commit e45bbaf has been approved by |
…=RalfJung Add MemoryExtra in InterpretCx constructor params This is to avoid modifying `MemoryExtra` inside `InterpretCx` after initialization. Related miri PR: rust-lang/miri#792 r? @RalfJung
…=RalfJung Add MemoryExtra in InterpretCx constructor params This is to avoid modifying `MemoryExtra` inside `InterpretCx` after initialization. Related miri PR: rust-lang/miri#792 r? @RalfJung
…=RalfJung Add MemoryExtra in InterpretCx constructor params This is to avoid modifying `MemoryExtra` inside `InterpretCx` after initialization. Related miri PR: rust-lang/miri#792 r? @RalfJung
Rollup of 13 pull requests Successful merges: - #61545 (Implement another internal lints) - #62110 (Improve -Ztime-passes) - #62133 (Feature gate `rustc` attributes harder) - #62158 (Add MemoryExtra in InterpretCx constructor params) - #62168 (The (almost) culmination of HirIdification) - #62193 (Create async version of the dynamic-drop test) - #62369 (Remove `compile-pass` from compiletest) - #62380 (rustc_target: avoid negative register counts in the SysV x86_64 ABI.) - #62381 (Fix a typo in Write::write_vectored docs) - #62390 (Update README.md) - #62396 (remove Scalar::is_null_ptr) - #62406 (Lint on invalid values passed to x.py --warnings) - #62414 (Remove last use of mem::uninitialized in SGX) Failed merges: r? @ghost
This is to avoid modifying
MemoryExtrainsideInterpretCxafter initialization. Related miri PR: rust-lang/miri#792r? @RalfJung