-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[ConstProp] Use a BitSet<Local>
instead of IndexVec<Local, bool>
#71312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
r? @estebank (rust_highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit fc31f83c77c693f550e8ad26eaa3dacba34ad6f2 with merge 3054153994c0b4aabefabd27f22ef1761dc8bcd1... |
☀️ Try build successful - checks-azure |
Queued 3054153994c0b4aabefabd27f22ef1761dc8bcd1 with parent e7497a8, future comparison URL. |
Some small memory improvements. CPU seems to be a wash. Seems about as I expected. |
wall-time shows some potential improvements, but it might well be within the noise margin (which is quite high for wall-time). I suspect we should merge this though -- it seems like a bitset is going to behave better as we scale up (e.g., with hundreds of locals), at least from a memory usage perspective. r=me if you feel similarly on the changes (including if you fix my nit along the way) |
fc31f83
to
c183b4c
Compare
@bors r=Mark-Simulacrum rollup=never (perf) |
📌 Commit c183b4c has been approved by |
@bors p=1 |
⌛ Testing commit c183b4c with merge dd27760a008fba35ef8091f1d72a3e86a80758f7... |
💔 Test failed - checks-azure |
Kind of looks like it timed out on macOS? |
looks spurious @bors retry |
⌛ Testing commit c183b4c with merge 37584210e6da6d45c84443526fc114e8bd83f6e0... |
💔 Test failed - checks-azure |
@bors retry |
☀️ Test successful - checks-azure |
No description provided.