From: Andrew Cagney <ac131313@ges.redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa:doco] document frame_align()
Date: Wed, 18 Sep 2002 09:24:00 -0000 [thread overview]
Message-ID: <3D88A8BB.2010007@ges.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 125 bytes --]
Hello,
This documents the frame_align() architecture method. It also clarifies
the behavior of stack_align().
ok?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1849 bytes --]
2002-09-18 Andrew Cagney <ac131313@redhat.com>
* gdbint.texinfo (Target Architecture Definition): Revise
description of STACK_ALIGN. Add description of FRAME_ALIGN.
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.100
diff -u -r1.100 gdbint.texinfo
--- gdbint.texinfo 24 Aug 2002 00:21:37 -0000 1.100
+++ gdbint.texinfo 18 Sep 2002 16:19:24 -0000
@@ -3175,6 +3175,23 @@
represented by @var{fi} does not have a stack frame associated with it.
Otherwise return 0.
+@item frame_align (@var{address})
+@anchor frame_align
+@findex frame_align
+Define this to adjust @var{address} so that it meets the alignment
+requirements for the start of a new stack frame. A stack frame's
+alignment requirements are typically stronger than a target processors
+stack alignment requirements (@pxref{STACK_ALIGN}).
+
+This function is used to ensure that, when creating a dummy frame, both
+the initial stack pointer and (if needed) the address of the return
+value are correctly aligned.
+
+Unlike @ref{STACK_ALIGN}, this function always adjusts the address in
+the direction of stack growth.
+
+By default, no frame based stack alignment is performed.
+
@item FRAME_ARGS_ADDRESS_CORRECT
@findex FRAME_ARGS_ADDRESS_CORRECT
See @file{stack.c}.
@@ -3690,9 +3707,15 @@
done.
@item STACK_ALIGN (@var{addr})
+@anchor{STACK_ALIGN}
@findex STACK_ALIGN
-Define this to adjust the address to the alignment required for the
-processor's stack.
+Define this to increase @var{addr} so that it meets the alignment
+requirements for the processor's stack.
+
+Unlike @ref{frame_align}, this function always adjusts @var{addr}
+upwards.
+
+By default, no stack alignment is performed.
@item STEP_SKIPS_DELAY (@var{addr})
@findex STEP_SKIPS_DELAY
next reply other threads:[~2002-09-18 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 9:24 Andrew Cagney [this message]
2002-09-18 9:29 ` Richard Earnshaw
2002-09-18 10:05 ` Andrew Cagney
2002-09-19 6:03 ` Eli Zaretskii
2002-09-19 8:29 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D88A8BB.2010007@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox