refactor: take use of secp256k1_scalar_{zero,one} constants #1330

pull theStack wants to merge 2 commits into bitcoin-core:master from theStack:use_zero_one_scalar_constants changing 4 files +53 −62
  1. theStack commented at 11:19 pm on May 29, 2023: contributor
    Rather than allocating a (non-constant) scalar variable on the stack with the sole purpose of setting it to a constant value, the global constants secp256k1_scalar_{zero,one} (apparently introduced in 34a67c773b0871e5797c7ab506d004e80911f120, PR #710) can be directly used instead for the values 0 or 1. There is very likely not even a difference in run-time, but it leads to simpler and less code which might be nice.
  2. in src/tests.c:4639 in 94b85556a6 outdated
    4635@@ -4643,7 +4636,7 @@ static int ecmult_multi_false_callback(secp256k1_scalar *sc, secp256k1_ge *pt, s
    4636 
    4637 static void test_ecmult_multi(secp256k1_scratch *scratch, secp256k1_ecmult_multi_func ecmult_multi) {
    4638     int ncount;
    4639-    secp256k1_scalar szero;
    4640+    const secp256k1_scalar szero = secp256k1_scalar_zero;
    


    real-or-random commented at 7:36 am on May 30, 2023:
    Why not get rid of szero entirely?

    theStack commented at 10:28 am on May 30, 2023:
    Kept it due to some irrational “diff will get too large, lines will get too long” thoughts and a portion of laziness 😅 Done now.
  3. in src/tests.c:1 in 94b85556a6


    real-or-random commented at 7:38 am on May 30, 2023:
    Can you add tests that check that the constants match what you get with secp256k1_scalar_set_int?

    theStack commented at 10:30 am on May 30, 2023:
    Thanks, done. Also put secp256k1_scalar_is_{zero,one} checks in.
  4. real-or-random commented at 7:38 am on May 30, 2023: contributor
    Concept ACK
  5. refactor: take use of `secp256k1_scalar_{zero,one}` constants 654246c635
  6. tests: add checks for scalar constants `secp256k1_scalar_{zero,one}` ade5b36701
  7. theStack force-pushed on May 30, 2023
  8. real-or-random approved
  9. real-or-random commented at 11:53 am on May 30, 2023: contributor
    utACK ade5b367018a624ff7ca1ecbb4a64889d47b0142
  10. real-or-random added the label refactor on May 30, 2023
  11. sipa commented at 4:49 pm on May 31, 2023: contributor
    utACK ade5b367018a624ff7ca1ecbb4a64889d47b0142
  12. real-or-random merged this on May 31, 2023
  13. real-or-random closed this on May 31, 2023

  14. theStack deleted the branch on May 31, 2023
  15. vmta referenced this in commit e1120c94a1 on Jun 4, 2023
  16. sipa referenced this in commit 901336eee7 on Jun 21, 2023
  17. vmta referenced this in commit 8f03457eed on Jul 1, 2023
  18. hebasto referenced this in commit 270d2b37b8 on Jul 21, 2023
  19. theStack cross-referenced this on Aug 1, 2023 from issue refactor: take use of `secp256k1_scalar_{zero,one}` constants (part 2) by theStack

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin-core/secp256k1. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-10-30 07:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me