This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
PATCH: Doc fix for mn10300_analyze_prologue
- From: Jim Blandy <jimb at zwingli dot cygnus dot com>
- To: gdb-patches at sources dot redhat dot com
- Date: Sun, 25 Nov 2001 18:46:03 -0500 (EST)
- Subject: PATCH: Doc fix for mn10300_analyze_prologue
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.