From: Jim Blandy <jimb@zwingli.cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: Doc fix for mn10300_analyze_prologue
Date: Sun, 11 Nov 2001 08:58:00 -0000 [thread overview]
Message-ID: <20011125234603.8BA615E9D8@zwingli.cygnus.com> (raw)
Message-ID: <20011111085800.54P84SPwBFCI5Uj-lmM1VMGl_7AxPH7JT-cZ6s6K4-Q@z> (raw)
2001-11-25 Jim Blandy <jimb@redhat.com>
* mn10300-tdep.c (mn10300_analyze_prologue): Doc fixes.
Index: mn10300-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mn10300-tdep.c,v
retrieving revision 1.22
diff -c -c -b -F'^(' -r1.22 mn10300-tdep.c
*** mn10300-tdep.c 2001/10/10 21:22:44 1.22
--- mn10300-tdep.c 2001/11/25 23:42:57
***************
*** 294,300 ****
In gcc/config/mn13000/mn10300.c, the expand_prologue prologue
function is pretty readable, and has a nice explanation of how the
prologue is generated. The prologues generated by that code will
! have the following form:
+ If this is an old-style varargs function, then its arguments
need to be flushed back to the stack:
--- 294,301 ----
In gcc/config/mn13000/mn10300.c, the expand_prologue prologue
function is pretty readable, and has a nice explanation of how the
prologue is generated. The prologues generated by that code will
! have the following form (NOTE: the current code doesn't handle all
! this!):
+ If this is an old-style varargs function, then its arguments
need to be flushed back to the stack:
***************
*** 322,327 ****
--- 323,331 ----
fmov fsN,(OFFSETN,sp)
fmov fsM,(OFFSETM,sp)
...
+
+ Note that, if OFFSETN happens to be zero, you'll get the
+ different opcode: fmov fsN,(sp)
. Or, set a0 to the start of the save area, and then use
post-increment addressing to save the FP registers.
next reply other threads:[~2001-11-25 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 15:44 Jim Blandy [this message]
2001-11-11 8:58 ` Jim Blandy
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=20011125234603.8BA615E9D8@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.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