feat: Sync from aztec-packages #4564
Closed
Conversation
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
### CVC5 Recently `cvc5` updated their api and changed the way of creating and managing terms. Now `cvc5::TermManger` is responsible for this instead of `cvc5::Solver`. This pr fixes our api to meet their update. Also I made `cvc5` an external project in CMakeLists so now you don't have to install it manually. ### Bool For some reason `Bool` class had pure `cvc5::Solver` pointer as a member. Fixed that to be `smt_solver::Solver`. ### Circuit fixed `univariate_flag`. It was `true` by default, so it performed the wrong optimization. ### Solver renamed - `fp` -> `ff_sort` - `s` -> `solver` - `tm` -> `term_manager` Added placeholder methods `getValue` and `assertFormula` to avoid code like `solver->solver.assertFormula` --------- Co-authored-by: Innokentii Sennovskii <[email protected]>
sirasistant
approved these changes
Mar 15, 2024
|
This is going to need a new bb version in order to pass tests afaik. Were these changes included in the release today? |
|
Ah true, forgot about the serialization change. I don't think it's released yet! |
|
Oh, it went in in 0.28. Will try updating, let's see AztecProtocol/aztec-packages#5192 |
Introduces earthly as an alternative CI that hopes to eventually replace our current build-system. https://docs.earthly.dev/ is a build system that combines Makefiles and Dockerfiles. This is basically exactly what our system needed, IMO, and has some nice things figured out. Hope is to reduce complexity of working with the build system by a good chunk. Core changes: - we have a github actions CI that runs a single end to end test inside earthly for arm64 and x86_64 - new Earthfile's now mirror the Dockerfile's, notable differences: - we build our own foundry package for ARM support - we build our own wasi-sdk package for ARM support - grumpkin SRS is no longer generated on the spot, but downloaded like bn254 SRS - we don't inject any commit hashes for Noir as this would cause spurious rebuilds as any difference stops caching, instead we inject a content hash (to be revisited) Side changes: - since we build our own wasi-sdk 21 package, and it is clang18, some compilation workarounds - allow specifying a different nargo and acvm binary in build - small output tweaks --------- Co-authored-by: Charlie Lye <[email protected]> Co-authored-by: Innokentii Sennovskii <[email protected]> Co-authored-by: Cody Gunton <[email protected]> Co-authored-by: Alex Gherghisan <[email protected]> Co-authored-by: Mitchell Tracy <[email protected]> Co-authored-by: Jan Beneš <[email protected]> Co-authored-by: esau <[email protected]> Co-authored-by: Facundo <[email protected]> Co-authored-by: josh crites <[email protected]> Co-authored-by: Tom French <[email protected]> Co-authored-by: Álvaro Rodríguez <[email protected]> Co-authored-by: Ilyas Ridhuan <[email protected]>
Introduces earthly as an alternative CI that hopes to eventually replace our current build-system. https://docs.earthly.dev/ is a build system that combines Makefiles and Dockerfiles. This is basically exactly what our system needed, IMO, and has some nice things figured out. Hope is to reduce complexity of working with the build system by a good chunk. Core changes: - we have a github actions CI that runs a single end to end test inside earthly for arm64 and x86_64 - new Earthfile's now mirror the Dockerfile's, notable differences: - we build our own foundry package for ARM support - we build our own wasi-sdk package for ARM support - grumpkin SRS is no longer generated on the spot, but downloaded like bn254 SRS - we don't inject any commit hashes for Noir as this would cause spurious rebuilds as any difference stops caching, instead we inject a content hash (to be revisited) Side changes: - since we build our own wasi-sdk 21 package, and it is clang18, some compilation workarounds - allow specifying a different nargo and acvm binary in build - small output tweaks --------- Co-authored-by: Charlie Lye <[email protected]> Co-authored-by: Innokentii Sennovskii <[email protected]> Co-authored-by: Cody Gunton <[email protected]> Co-authored-by: Alex Gherghisan <[email protected]> Co-authored-by: Mitchell Tracy <[email protected]> Co-authored-by: Jan Beneš <[email protected]> Co-authored-by: esau <[email protected]> Co-authored-by: Facundo <[email protected]> Co-authored-by: josh crites <[email protected]> Co-authored-by: Tom French <[email protected]> Co-authored-by: Álvaro Rodríguez <[email protected]> Co-authored-by: Ilyas Ridhuan <[email protected]>
) * Add storage e2e tests * Convert test contract methods to snake case to match other contracts. * Remove `avm_` requirement in function names for transpilation. It's not needed, we rely on `#[aztec(public-vm)]`. * Prepare ground in bootstrap.sh to transpile all files in parallel. It works but I'm being overly cautious and not enabling it on all files until I need it. * Backup original contract before transpiling.
) * Add storage e2e tests * Convert test contract methods to snake case to match other contracts. * Remove `avm_` requirement in function names for transpilation. It's not needed, we rely on `#[aztec(public-vm)]`. * Prepare ground in bootstrap.sh to transpile all files in parallel. It works but I'm being overly cautious and not enabling it on all files until I need it. * Backup original contract before transpiling.
|
Closing to try to fix sync |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated pull of Noir development from aztec-packages.
BEGIN_COMMIT_OVERRIDE
chore(avm-simulator): update e2e test (AztecProtocol/aztec-packages#5283)
feat!: Acir call opcode (AztecProtocol/aztec-packages#4773)
feat: initial Earthly CI (AztecProtocol/aztec-packages#5069)
feat: Check initializer msg.sender matches deployer from address preimage (AztecProtocol/aztec-packages#5222)
feat: Sync from noir (AztecProtocol/aztec-packages#5234)
feat: Brillig IR refactor (AztecProtocol/aztec-packages#5233)
feat(avm): brillig CONST of size > u128 (AztecProtocol/aztec-packages#5217)
feat: New brillig field operations and refactor of binary operations (AztecProtocol/aztec-packages#5208)
feat!: Support contracts with no constructor (AztecProtocol/aztec-packages#5175)
END_COMMIT_OVERRIDE