-
Notifications
You must be signed in to change notification settings - Fork 94
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
WASI-20. Low memory prover (512k possible). Native pthread support (15s wasm time). #434
Merged
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
…rg into cl/wasm_pthread
…rg into cl/wasm_pthread
Charlie gave me a tour of changes relevant to the cryptography team. Otherwise we are foregoing a review due to the massive scope, the amount of new code, the fact that things are very much in flux, and the fact that this is not intended for production. |
ludamad
pushed a commit
to AztecProtocol/aztec-packages
that referenced
this pull request
Jul 22, 2023
…5s wasm time). (AztecProtocol/barretenberg#434) * Remove foundation submodule, add build-system * Initial bindgen work. * GPT4 created rust bindgen. * Debug build preset wasm-dbg for stack traces etc. * Async call support. Refactor binds. Common is module. WASM stubs unused wasi. * Move some c_bind to module root and make use new abi. * Initial working pthreads. * Polynomial cache * Custom poly allocator. Prealloc. * Cleanup. Several parallel_for solutions. Might be worth keeping them around until threading work stabilises. * Improve mem usage by slab allocating large parts of pippenger runtime state, and allowing slab reuse by removing from pk. * Don't need binaryen. * Bump alpine to get clang 16 * Backwards compatible cbinds. * Move slab allocator to common. Init slab allocator just before creating pk. * Dont need bleeding edge fork of libc anymore * bb.js is standalone prover that handles noir constraint/witness output. (AztecProtocol/barretenberg#471) * format msgpack serialization and excldue msgpack-c from clang-format (AztecProtocol/barretenberg#467) * Fix horrific nasty memory bug. --------- Co-authored-by: Suyash Bagad <suyashnbagad1997@gmail.com> Co-authored-by: Maxim Vezenov <mvezenov@gmail.com> Co-authored-by: Maddiaa <47148561+Maddiaa0@users.noreply.github.com> Co-authored-by: ledwards2225 <98505400+ledwards2225@users.noreply.github.com> Co-authored-by: Innokentii Sennovskii <isennovskiy@gmail.com> Co-authored-by: kevaundray <kevtheappdev@gmail.com> Co-authored-by: zac-williamson <blorktronics@gmail.com> Co-authored-by: codygunton <codygunton@gmail.com>
ludamad
pushed a commit
to AztecProtocol/aztec-packages
that referenced
this pull request
Jul 24, 2023
…5s wasm time). (AztecProtocol/barretenberg#434) * Remove foundation submodule, add build-system * Initial bindgen work. * GPT4 created rust bindgen. * Debug build preset wasm-dbg for stack traces etc. * Async call support. Refactor binds. Common is module. WASM stubs unused wasi. * Move some c_bind to module root and make use new abi. * Initial working pthreads. * Polynomial cache * Custom poly allocator. Prealloc. * Cleanup. Several parallel_for solutions. Might be worth keeping them around until threading work stabilises. * Improve mem usage by slab allocating large parts of pippenger runtime state, and allowing slab reuse by removing from pk. * Don't need binaryen. * Bump alpine to get clang 16 * Backwards compatible cbinds. * Move slab allocator to common. Init slab allocator just before creating pk. * Dont need bleeding edge fork of libc anymore * bb.js is standalone prover that handles noir constraint/witness output. (AztecProtocol/barretenberg#471) * format msgpack serialization and excldue msgpack-c from clang-format (AztecProtocol/barretenberg#467) * Fix horrific nasty memory bug. --------- Co-authored-by: Suyash Bagad <suyashnbagad1997@gmail.com> Co-authored-by: Maxim Vezenov <mvezenov@gmail.com> Co-authored-by: Maddiaa <47148561+Maddiaa0@users.noreply.github.com> Co-authored-by: ledwards2225 <98505400+ledwards2225@users.noreply.github.com> Co-authored-by: Innokentii Sennovskii <isennovskiy@gmail.com> Co-authored-by: kevaundray <kevtheappdev@gmail.com> Co-authored-by: zac-williamson <blorktronics@gmail.com> Co-authored-by: codygunton <codygunton@gmail.com>
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.
barretenberg
Wins:
-DOMP_MULTITHREADING=OFF
).simple.rawtest.ts
works in node and when compiled to browser via webpack.How:
bb.js
We are moving towards standalone prover/verifier binaries to be maintained by bb team(s), and to be consumed by noir team(s) (and whoever else).
This is the first implementation of such a prover/verifier.
Wins: