This is the mail archive of the gcc-patches@gcc.gnu.org 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: [stack] Automatic Stack Aligment Support


On Thu, Mar 20, 2008 at 10:33:10PM +0100, Ralf Wildenhues wrote:
> * Ye, Joey wrote on Thu, Mar 20, 2008 at 01:50:33PM CET:
> > 2008-03-19  Joey Ye  <joey.ye@intel.com>
> > 	    H.J. Lu  <hongjiu.lu@intel.com>
> > 	    Xuepeng Guo  <xuepeng.guo@intel.com>
> [...]
> > --- doc/extend.texi	(.../fsf/trunk/gcc/doc)	(revision 1884)
> > +++ doc/extend.texi	(.../branches/stack-frame/gcc/doc)
> > (revision 1884)
> > @@ -2701,17 +2701,13 @@
> [...]
> > +The @code{force_align_arg_pointer} attribute may be applied to
> > +individual function definitions, assuming that the runtime stack is
> > +aligned according to the psABI and generating an alternate
> > +prologue/aepilogue that realigns the runtime stack if necessary. 
> 
> s/aepilogue/epilogue/
> 
> > --- doc/invoke.texi	(.../fsf/trunk/gcc/doc)	(revision 1884)
> > +++ doc/invoke.texi	(.../branches/stack-frame/gcc/doc)
> [...]
> > @@ -10721,6 +10719,12 @@
> >  byte boundary.  If @option{-mpreferred-stack-boundary} is not
> > specified,
> >  the default is 4 (16 bytes or 128 bits).
> >  
> > +@item -mincoming-stack-boundary=@var{num}
> > +@opindex mincoming-stack-boundary
> > +Assume the incoming stack aligned to a 2 raised to @var{num} byte
> 
> s/stack/& is/
> 
> > +boundary.  If @option{-mincoming-stack-boundary} is not specified,
> > +the one specified by @option{-mpreferred-stack-boundary} will be used.

I am checking it into stack branch.

Thanks.


H.J.
---
Index: gcc/doc/extend.texi
===================================================================
--- gcc/doc/extend.texi	(revision 1866)
+++ gcc/doc/extend.texi	(working copy)
@@ -2704,7 +2704,7 @@ floating point arguments on the stack.
 The @code{force_align_arg_pointer} attribute may be applied to
 individual function definitions, assuming that the runtime stack is
 aligned according to the psABI and generating an alternate
-prologue/aepilogue that realigns the runtime stack if necessary. 
+prologue/epilogue that realigns the runtime stack if necessary. 
 On the Intel x86, this supports mixing codes that keep a 4-byte aligned
 stack, as specified by i386 psABI, with codes that need a 16-byte
 aligned stack, as required by SSE instructions. 
Index: gcc/doc/invoke.texi
===================================================================
--- gcc/doc/invoke.texi	(revision 1866)
+++ gcc/doc/invoke.texi	(working copy)
@@ -10721,7 +10721,7 @@ the default is 4 (16 bytes or 128 bits).
 
 @item -mincoming-stack-boundary=@var{num}
 @opindex mincoming-stack-boundary
-Assume the incoming stack aligned to a 2 raised to @var{num} byte
+Assume the incoming stack is aligned to a 2 raised to @var{num} byte
 boundary.  If @option{-mincoming-stack-boundary} is not specified,
 the one specified by @option{-mpreferred-stack-boundary} will be used.
 


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