md5/sha512: a better fix for strict aliasing warnings

The locations *are* well-aligned for direct stores
on any architecture.

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/libbb/hash_md5_sha.c b/libbb/hash_md5_sha.c
index e10cb391d..3f743ac75 100644
--- a/libbb/hash_md5_sha.c
+++ b/libbb/hash_md5_sha.c
@@ -84,7 +84,7 @@ static void FAST_FUNC common64_end(md5_ctx_t *ctx, int swap_needed)
                         if (swap_needed)
                                 t = bb_bswap_64(t);
                         /* wbuffer is suitably aligned for this */
-                        memcpy(&ctx->wbuffer[64 - 8], &t, sizeof(t));
+                        *(bb__aliased_uint64_t *) (&ctx->wbuffer[64 - 8]) = t;
                 }
                 ctx->process_block(ctx);
                 if (remaining >= 8)
@@ -883,10 +883,10 @@ void FAST_FUNC sha512_end(sha512_ctx_t *ctx, void *resbuf)
                         uint64_t t;
                         t = ctx->total64[0] << 3;
                         t = SWAP_BE64(t);
-                        memcpy(&ctx->wbuffer[128 - 8], &t, sizeof(t));
+                        *(bb__aliased_uint64_t *) (&ctx->wbuffer[128 - 8]) = t;
                         t = (ctx->total64[1] << 3) | (ctx->total64[0] >> 61);
                         t = SWAP_BE64(t);
-                        memcpy(&ctx->wbuffer[128 - 16], &t, sizeof(t));
+                        *(bb__aliased_uint64_t *) (&ctx->wbuffer[128 - 16]) = t;
                 }
                 sha512_process_block128(ctx);
                 if (remaining >= 16)