Patchwork Fix minor oversight in stack checking patch series

login
register
mail settings
Submitter Eric Botcazou
Date May 11, 2011, 3:16 p.m.
Message ID <201105111716.31114.ebotcazou@adacore.com>
Download mbox | patch
Permalink /patch/95159/
State New
Headers show

Comments

Eric Botcazou - May 11, 2011, 3:16 p.m.
We don't need to initialize stack_check_probe_note in all cases now, but only 
if the mechanism is the generic one.

Tested on i586-suse-linux, applied on the mainline as obvious.


2011-05-11  Eric Botcazou  <ebotcazou@adacore.com>

	* function.c (expand_function_start): Initialize stack_check_probe_note
	only if the generic stack checking mechanism is used.

Patch

Index: function.c
===================================================================
--- function.c	(revision 173643)
+++ function.c	(working copy)
@@ -4813,9 +4813,8 @@  expand_function_start (tree subr)
 #endif
     }
 
-  /* After the display initializations is where the stack checking
-     probe should go.  */
-  if(flag_stack_check)
+  /* If we are doing generic stack checking, the probe should go here.  */
+  if (flag_stack_check == GENERIC_STACK_CHECK)
     stack_check_probe_note = emit_note (NOTE_INSN_DELETED);
 
   /* Make sure there is a line number after the function entry setup code.  */