-
Notifications
You must be signed in to change notification settings - Fork 17
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
logup multiplicity in witness assignment #198
Conversation
819edf3
to
96d357e
Compare
94527e6
to
1c777b5
Compare
1c777b5
to
ca0a364
Compare
@@ -1,5 +1,6 @@ | |||
#![feature(box_patterns)] | |||
#![feature(stmt_expr_attributes)] | |||
#![feature(variant_count)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is for mem::variant_count::()] to count entries of ROMType
Can we make it to support byte logical operations besides range check? |
Yes it can, and I just push a new commit as a demo The scope of lk_multiplicitty is just keep |
d02ba40
to
7ddc98e
Compare
e422cc2
to
56ea314
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
To address comment #198 (comment) For further reduce the Arc clone overhead. I think in the future we might redesign `assign_instances` to support streaming assign in the future, such that StepRecord will emit as streaming from emulator and multi-threads as worker to collect batch data and do assignment. We can explore further usage when tuning performance
a lock-free, thread-safe structure to count lookup multiplicicity for opcode witness assignment The lock-free, thread-safe structure is to support streaming witness assignment from emulator. Emulator emit a steptrace and insert to channel, while multi-thread are fetch step from channel and do the instance assighment concurrently while still updating the same logup multiplicity in some shared matters
To address comment #198 (comment) For further reduce the Arc clone overhead. I think in the future we might redesign `assign_instances` to support streaming assign in the future, such that StepRecord will emit as streaming from emulator and multi-threads as worker to collect batch data and do assignment. We can explore further usage when tuning performance
a lock-free, thread-safe structure to count lookup multiplicicity for opcode witness assignment
The lock-free, thread-safe structure is to support streaming witness assignment from emulator. Emulator emit a steptrace and insert to channel, while multi-thread are fetch step from channel and do the instance assighment concurrently while still updating the same logup multiplicity in some shared matters