From 3948beeb403e69da4ce7096191b6ee5159b1dedc Mon Sep 17 00:00:00 2001 From: sof Date: Sun, 5 Oct 1997 20:44:20 +0000 Subject: [PATCH] [project @ 1997-10-05 20:44:20 by sof] doc update --- ghc/includes/COptJumps.lh | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/ghc/includes/COptJumps.lh b/ghc/includes/COptJumps.lh index c31adbe..9786cd4 100644 --- a/ghc/includes/COptJumps.lh +++ b/ghc/includes/COptJumps.lh @@ -37,10 +37,9 @@ variant, too, for that matter). GCC will have assumed that pushing/popping of C-stack frames is going on when it generated its code, and used stack space accordingly. However, we actually {\em post-process away} all such stack-framery -(see \tr{ghc/driver/ghc-asm.lprl}). -Thing will be OK however, if we initially make sure there are -@RESERVED_C_STACK_BYTES@ on the C-stack to begin with, for local -variables. +(see \tr{ghc/driver/ghc-asm.lprl}). Things will be OK however, if we +initially make sure there are @RESERVED_C_STACK_BYTES@ on the C-stack +to begin with, for local variables. \begin{code} #define RESERVED_C_STACK_BYTES (512 * sizeof(I_)) /* MUST BE OF GENEROUS ALIGNMENT */ @@ -327,7 +326,7 @@ extern void __DISCARD__(STG_NO_ARGS); "\tmovl 12(%%eax),%%ebp" \ : : "n" (RESERVED_C_STACK_BYTES) : "%eax"); -#endif /* __i[34]86__ */ +#endif /* __i[3456]86__ */ \end{code} %************************************************************************ -- 1.7.10.4