-
Notifications
You must be signed in to change notification settings - Fork 301
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor: ProvingKey has ProverPolynomials (#5940)
Updates all proving systems (except AVM) to have a single storage container for polynomials: a `ProverPolynomials` object belonging to the `ProvingKey`. The old model: Two containers for polynomials: `ProvingKey` (via inheritance from `PrecomputedEntities` and `WitnessEntities`) and a `ProverPolynomials` owned by the `ProverInstance`. Both of these containers store genuine Polynomials, but the memory is "shared" so neither was any more the owner of the polys than the other. This led to lots of boilerplate for sharing polys between the two containers and confusion about what needed to be shared when. There were also several places where we would construct a temporary ProverPolynomials for use in one round (e.g. grand product computation which needs shifts) only to destroy it immediately afterwards. Note: it used to make sense to have both ProvingKey and ProverPolynomials when ProvingKey was not a Flavor-style object. I.e. it used to be a collection of different vectors of polys, so we needed to construct ProverPolynomials as the nice container for sumcheck to operate on. But as soon as ProvingKey became a thing inheriting from Precomputed Entities and WitnessEntities, this no longer made sense. Closes AztecProtocol/barretenberg#962 Branch: `ClientIVCBench/Full/6 21403 ms 16242 ms 1` Master `ClientIVCBench/Full/6 21585 ms 16480 ms 1`
- Loading branch information
1 parent
e615a83
commit 0a64279
Showing
42 changed files
with
668 additions
and
1,015 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.