This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PING PATCH]: Fix PR 34013 save red-zone while stack probing for x86_64


> 2007-12-13  Arthur Norman <>

>        * gcc/config/i386/i386.c: (ix86_expand_prologue): Save red-zone
> while stack probing.

No gcc/ and no ":" before the function name. Perhaps more descriptive
wording would be:

* config/i386/i386.c (ix86_expand_prologue): Do not use
ix86_emit_save_regs_using_mov when

Is it possible to construct a testcase from the code that was posted
in the PR audit trai?

Also, "&&" shouold go in a new line, and please change the logic into
something without double negations, perhaps into something as in the
attached version of the patch.


Index: i386.c
--- i386.c      (revision 131032)
+++ i386.c      (working copy)
@@ -6318,8 +6318,12 @@
     allocate += frame.nregs * UNITS_PER_WORD;

   /* When using red zone we may start register saving before allocating
-     the stack frame saving one cycle of the prologue.  */
-  if (TARGET_RED_ZONE && frame.save_regs_using_mov)
+     the stack frame saving one cycle of the prologue. However I will
+     avoid doing this if I am going to have to probe the stack since
+     at least on x86_64 the stack probe can turn into a call that clobbers
+     a red zone location */
+  if (TARGET_RED_ZONE && frame.save_regs_using_mov
+      && (! TARGET_STACK_PROBE || allocate < CHECK_STACK_LIMIT))
     ix86_emit_save_regs_using_mov (frame_pointer_needed ?
                                   : stack_pointer_rtx,
                                   -frame.nregs * UNITS_PER_WORD);
@@ -6375,7 +6379,9 @@

-  if (frame.save_regs_using_mov && !TARGET_RED_ZONE)
+  if (frame.save_regs_using_mov
+      && !(TARGET_RED_ZONE
+          && (! TARGET_STACK_PROBE || allocate < CHECK_STACK_LIMIT)))
       if (!frame_pointer_needed || !frame.to_allocate)
         ix86_emit_save_regs_using_mov (stack_pointer_rtx, frame.to_allocate);

The patch is OK (but please wait for possible comments from mingw maintainer)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]