Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bb should allow querying which opcodes it supports #1922

Closed
TomAFrench opened this issue Aug 31, 2023 · 0 comments · Fixed by #2010
Closed

bb should allow querying which opcodes it supports #1922

TomAFrench opened this issue Aug 31, 2023 · 0 comments · Fixed by #2010
Labels
C-bb.js Component: bb.js - wrapping bberg in js

Comments

@TomAFrench
Copy link
Member

When generating ACIR we need to know which opcodes the backend supports in order to fallback to simpler opcodes appropriately. Barretenberg's supported opcodes are currently hardcoded inside Nargo.

For dynamic backends we need to be able to pull the opcode support from the backend itself, so bb needs to expose this information in some manner.
@github-project-automation github-project-automation bot moved this to Todo in A3 Aug 31, 2023
@TomAFrench TomAFrench added this to Noir Sep 1, 2023
@TomAFrench TomAFrench self-assigned this Sep 1, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Noir Sep 1, 2023
@TomAFrench TomAFrench removed their assignment Sep 1, 2023
@TomAFrench TomAFrench added the C-bb.js Component: bb.js - wrapping bberg in js label Sep 4, 2023
@TomAFrench TomAFrench mentioned this issue Sep 5, 2023
Merged
5 tasks
@kevaundray kevaundray mentioned this issue Sep 5, 2023
Merged
4 tasks
kevaundray added a commit that referenced this issue Sep 5, 2023
@kevaundray @TomAFrench
feat: Add info command to bb (#2010)
1fd8196 
Resolves #1922 
Resolves #1923 

# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [ ] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [ ] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [ ] Every change is related to the PR description.
- [ ] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).

---------

Co-authored-by: Tom French <[email protected]>
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Sep 5, 2023
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in Noir Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-bb.js Component: bb.js - wrapping bberg in js
Projects
A3
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Add info command to bb AztecProtocol/aztec-packages
1 participant
@TomAFrench