Misc changes related to Miri allocations#50520
Conversation
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
☔ The latest upstream changes (presumably #50395) made this pull request unmergeable. Please resolve the merge conflicts. |
|
☔ The latest upstream changes (presumably #50249) made this pull request unmergeable. Please resolve the merge conflicts. |
|
☔ The latest upstream changes (presumably #50710) made this pull request unmergeable. Please resolve the merge conflicts. |
oli-obk
left a comment
There was a problem hiding this comment.
As discussed on IRC I am very unsure about the last commit. We had a scheme like that when miri was merged, and we kept running into various edge cases with the decoding order. Even creating MCVEs for the panics we were getting was hard, because small changes in the code would change the order of evaluation.
src/librustc/ich/impls_ty.rs
Outdated
There was a problem hiding this comment.
This implementation could be replaced by a impl_stable_hash_for! macro call
There was a problem hiding this comment.
I don't think we have a macro which works for enums with lifetimes.
|
I've split the last commit into a separate PR. |
src/bootstrap/lib.rs
Outdated
There was a problem hiding this comment.
Please put this in a separate PR, I have no idea what this does or why it's here
|
@bors r+ |
|
📌 Commit ddc5418 has been approved by |
|
☀️ Test successful - status-appveyor, status-travis |
|
FWIW this hurt the max-rss usage on a few benchmarks (but not by huge amounts) |
|
Might be due to the removed cache for strings and byte strings |
This builds on top of #50249
r? @oli-obk