-
Notifications
You must be signed in to change notification settings - Fork 524
Enhancement: Re-enable fillBytes method in ABI and eval.go implementation
#3856
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3856 +/- ##
==========================================
- Coverage 49.97% 49.97% -0.01%
==========================================
Files 393 393
Lines 68390 68353 -37
==========================================
- Hits 34181 34160 -21
+ Misses 30473 30464 -9
+ Partials 3736 3729 -7
Continue to review full report at Codecov.
|
fillBytes method in ABI implementationfillBytes method in ABI and eval.go implementation
michaeldiamant
left a comment
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.
| } | ||
| } else if fs.field == Secp256r1 { | ||
| x, y = unmarshalCompressed(elliptic.P256(), pubkey) | ||
| x, y = elliptic.UnmarshalCompressed(elliptic.P256(), pubkey) |
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.
Should we retest the speed of decompress to reconsider opcode cost? Or was our implementation the same as this library function?
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 previous (un)marshalCompressed was copying the library implementation, so I felt like this should not change the speed.
Description
The current go-algorand build is over golang 1.16, which means we can revert #3498.
#3498 is introduced for the sake of downgrading golang for perf issues, now we should lift back to earlier implementation.
We also re-enable
FillBytesinleadingZeroimplementation, and updateelliptic.(un)marshalCompressedfor #2852 .