aboutsummaryrefslogtreecommitdiff
path: root/gdb/mn10300-tdep.c
diff options
context:
space:
mode:
authorJim Blandy <jimb@codesourcery.com>2001-11-25 23:43:43 +0000
committerJim Blandy <jimb@codesourcery.com>2001-11-25 23:43:43 +0000
commit03a0cf8a7a512ba84f0d3d99ed94e63d5cf0ffcb (patch)
tree03bd0eea2d4106b5f7f8acfb3084f2aded0600a0 /gdb/mn10300-tdep.c
parent9edf3ae12acfba6829f7f7be0b1692aae6d2adc2 (diff)
downloadgdb-03a0cf8a7a512ba84f0d3d99ed94e63d5cf0ffcb.zip
gdb-03a0cf8a7a512ba84f0d3d99ed94e63d5cf0ffcb.tar.gz
gdb-03a0cf8a7a512ba84f0d3d99ed94e63d5cf0ffcb.tar.bz2
* mn10300-tdep.c (mn10300_analyze_prologue): Doc fixes.
Diffstat (limited to 'gdb/mn10300-tdep.c')
-rw-r--r--gdb/mn10300-tdep.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/gdb/mn10300-tdep.c b/gdb/mn10300-tdep.c
index 1e684f8..4a3e294 100644
--- a/gdb/mn10300-tdep.c
+++ b/gdb/mn10300-tdep.c
@@ -294,7 +294,8 @@ set_movm_offsets (struct frame_info *fi, int movm_args)
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:
+ 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:
@@ -323,6 +324,9 @@ set_movm_offsets (struct frame_info *fi, int movm_args)
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.