* mn10300-tdep.c (mn10300_analyze_prologue): Doc fixes.

diff --git a/gdb/mn10300-tdep.c b/gdb/mn10300-tdep.c
index 1e684f8cbbefe1272b292c197764d17234524ba4..4a3e2943fc3bc5f0c4737c0df7528470dfd84800 100644 (file)
--- 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.