-
Notifications
You must be signed in to change notification settings - Fork 11
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
fix: fix broken tests in runtime_bignum_test.nr
#39
Merged
Merged
Changes from 18 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
2bd6ade
Make test names unique. Now some fail.
charlielye 47a8700
fixing the failing tests
kashbrti 39fbdbb
temporarily fixed the tests failing with --force-brillig tests
kashbrti ffbc92e
fmt
kashbrti 260116a
Merge branch 'main' into cl/unique_test_names
TomAFrench 31761af
fmt
TomAFrench a5f3923
Merge branch 'main' into cl/unique_test_names
TomAFrench e835d6c
.
TomAFrench 1b09495
nuked unconstrained derive
kashbrti a247db2
fmt
kashbrti 90d5840
Merge branch 'main' into cl/unique_test_names
TomAFrench 59363d0
Update .gitignore
kashbrti d2cff3f
chore: remove unwanted file
TomAFrench 609e4a9
chore: remove temporary comments
TomAFrench 0136a26
Update src/fns/unconstrained_ops.nr
TomAFrench 6b88c3f
.
TomAFrench a93daea
revert accidental change
TomAFrench 2b7dae0
fmt
TomAFrench 3291763
Update src/tests/runtime_bignum_test.nr
TomAFrench 709669a
Apply suggestions from code review
TomAFrench 945deb4
chore: revert hack
TomAFrench File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,2 @@ | ||
target | ||
target | ||
.vscode/launch.json |
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.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests are all passing with the commented out range checks. Is this still an issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kashbrti
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the asserts that I've added are doing the range check if I'm not making a mistake.
The issue was that as
limb[N-1]
is not a constant, the range check was happening for the bit size of the native field rather than the actual input.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, I agree that the added asserts are going a less efficient range check.
Why would a non-constant field result in us not performing a check whether
limb[N-1]
fits withinMOD_BITS - (N-1)*120
bits?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you verify the output in the ACIR? If we're producing incorrect output here we shouldn't just hide that by rewriting the Noir.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be 100% clear, I'd like to restore the original calls to
assert_max_bit_size
so I'm keen to know why they were replaced and if it's due to a correctness issue in the compiler then we need to fix that.