Skip to content

Remove concept of virtualization level #1648

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

Open
wants to merge 2 commits into
base: testnet
Choose a base branch
from

Conversation

DanShaders
Copy link
Contributor

But for a single place in test-db, we used virtualization level 0 for non-virtualized cells and level 1 for virtualized ones. With this patch, we do not store this level anymore and instead infer it based on "effective" level (previously known as VirtualizationParameters::level) and the actual level of the cell.

This is mainly done to reduce cognitive complexity of the code. However, as a nice side-effect, changes in VirtualCell give a negligible performance improvement on the verification benchmark.

@DanShaders DanShaders changed the base branch from master to testnet May 4, 2025 03:25
DanShaders added 2 commits May 3, 2025 23:38
But for a single place in test-db, we used virtualization level 0 for
non-virtualized cells and level 1 for virtualized ones. With this patch,
we do not store this level anymore and instead infer it based on
"effective" level (previously known as VirtualizationParameters::level)
and the actual level of the cell.

This is mainly done to reduce cognitive complexity of the code. However,
as a nice side-effect, changes in VirtualCell give a negligible
performance improvement on the verification benchmark.
A well-known limitation of using ninja is that it requires the user to
pass -fcolor-diagnostics=always flag to the compiler to get colored
diagnostics. Starting from version 3.24, CMake can do this for us if we
set CMAKE_COLOR_DIAGNOSTICS flag to truthful value.
@DanShaders DanShaders force-pushed the virtualization-be-gone branch from 6c58028 to 0a2d87f Compare May 4, 2025 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant