You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the block and VM machine we have rows of cells that are writable. At some point their range constraints are deleted and only the value is stored (together with a flag to denote that the value is known). This process is called "finalization". At the end of witgen, the values are then stored into column vectors (while we had rows before), which is called transposition.
There is probably no real need for storing finalized rows and we could just do transposition at the point of finalization. We could do it less often than finalization to reduce the impact of memory cache misses.
The text was updated successfully, but these errors were encountered:
In the block and VM machine we have rows of cells that are writable. At some point their range constraints are deleted and only the value is stored (together with a flag to denote that the value is known). This process is called "finalization". At the end of witgen, the values are then stored into column vectors (while we had rows before), which is called transposition.
There is probably no real need for storing finalized rows and we could just do transposition at the point of finalization. We could do it less often than finalization to reduce the impact of memory cache misses.
The text was updated successfully, but these errors were encountered: