Moved SHA 512 work area to local stack

While some users could perhaps benefit from saving 640 bytes of stack
space by allocating the context statically, or in the heap, in practice
it's not he bottleneck.  Besides, putting the work area there actually
*increases* stack usage on signatures and signature verification, which
are the most stack hungry parts of Monocypher to begin with.

Better not try to be clever.

diff --git a/src/optional/ed25519.c b/src/optional/ed25519.c
index 2bb45458599138f3609c5f4a86b0a592e2859629..d19eede9df080d6b496881e9c5a6a15d4af95331 100644 (file)
--- a/src/optional/ed25519.c
+++ b/src/optional/ed25519.c
@@ -72,7 +72,7 @@ static const u64 K[80] = {
 
 static void sha512_compress(crypto_sha512_ctx *ctx)
 {
-    u64 *w = ctx->w;
+    u64 w[80];
     FOR(i,  0, 16) { w[i] = ctx->input[i]; }
     FOR(i, 16, 80) { w[i] = (lit_sigma1(w[i- 2]) + w[i- 7] +
                              lit_sigma0(w[i-15]) + w[i-16]); }

diff --git a/src/optional/ed25519.h b/src/optional/ed25519.h
index 3f5bff9b2070d70d1695a298a8e7be37c09e9de3..32cb5c4e3f8621c3ccaaa9cbd128b437712680f0 100644 (file)
--- a/src/optional/ed25519.h
+++ b/src/optional/ed25519.h
@@ -12,7 +12,6 @@
 // Do not rely on the size or content on any of those types,
 // they may change without notice.
 typedef struct {
-    uint64_t w[80]; // work area
     uint64_t hash[8];
     uint64_t input[16];
     uint64_t input_size[2];