diff --git a/sparc/aes-decrypt-internal.asm b/sparc/aes-decrypt-internal.asm
index ecc2712e259fa3ef043ed7390d63c93706fd0a8b..6318ca9fb624b325be1ab0d81be6b8c4dbf5fb7d 100644
--- a/sparc/aes-decrypt-internal.asm
+++ b/sparc/aes-decrypt-internal.asm
@@ -51,10 +51,8 @@ C The sparc32 stack frame looks like
 C
 C %fp -   4: OS-dependent link field
 C %fp -   8: OS-dependent link field
-C %fp -  24: tmp, uint32_t[4]
-C %fp -  40: wtxt, uint32_t[4]
-C %fp - 136: OS register save area. 
-define(<FRAME_SIZE>, 136)
+C %fp - 104: OS register save area. 
+define(<FRAME_SIZE>, 104)
 
 	.file "aes-decrypt-internal.asm"
 
diff --git a/sparc/aes-encrypt-internal.asm b/sparc/aes-encrypt-internal.asm
index 770117720868deff2942dff358fc57328bc11fd8..30937df042e8811403c8cb7a152aa2d8b6793006 100644
--- a/sparc/aes-encrypt-internal.asm
+++ b/sparc/aes-encrypt-internal.asm
@@ -47,14 +47,17 @@ C %g1 and %g2 are TMP1 and TMP2
 
 C Registers %g1-%g3 and %o0 - %o5 are free to use.
 
+C I'm still slightly confused by the frame layout, specified in
+C "SYSTEM V APPLICATION BINARY INTERFACE SPARC Processor Supplement".
+C However, Sun's cc generates a 104 byte stack frame for a function
+C with no local variables, so that should be good enough for us too.
+
 C The sparc32 stack frame looks like
 C
 C %fp -   4: OS-dependent link field
 C %fp -   8: OS-dependent link field
-C %fp -  24: tmp, uint32_t[4]
-C %fp -  40: wtxt, uint32_t[4]
-C %fp - 136: OS register save area. 
-define(<FRAME_SIZE>, 136)
+C %fp - 104: OS register save area 
+define(<FRAME_SIZE>, 104)
 
 	.file "aes-encrypt-internal.asm"