GCC Middle and Back End API Reference
stack-ptr-mod.c File Reference


static void notice_stack_pointer_modification_1 (rtx x, const_rtx pat, void *data)
static void notice_stack_pointer_modification ()
static unsigned int rest_of_handle_stack_ptr_mod ()
rtl_opt_passmake_pass_stack_ptr_mod ()

Function Documentation

rtl_opt_pass* make_pass_stack_ptr_mod ( )
static void notice_stack_pointer_modification ( )
     Assume that the stack pointer is unchanging if alloca hasn't
     been used.  
                 Check if insn modifies the stack pointer.  
     The value coming into this pass was 0, and the exit block uses
     are based on this.  If the value is now 1, we need to redo the
     exit block uses.  

References note_stores(), and notice_stack_pointer_modification_1().

static void notice_stack_pointer_modification_1 ( rtx  x,
const_rtx  pat,
void *  data 

Discover if the stack pointer is modified in a function. Copyright (C) 2007-2013 Free Software Foundation, Inc.

This file is part of GCC.

GCC is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3, or (at your option) any later version.

GCC is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with GCC; see the file COPYING3. If not see http://www.gnu.org/licenses/.

   Determine if the stack pointer is constant over the life of the function.
   Only useful before prologues have been emitted.  
         The stack pointer is only modified indirectly as the result
         of a push until later.  See the comments in rtl.texi
         regarding Embedded Side-Effects on Addresses.  

References RTX_AUTOINC.

Referenced by notice_stack_pointer_modification().

static unsigned int rest_of_handle_stack_ptr_mod ( )
     Some targets can emit simpler epilogues if they know that sp was
     not ever modified during the function.  After reload, of course,
     we've already emitted the epilogue so there's no sense searching.  

References RTL_PASS, and TV_NONE.