From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-10722-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 17138 invoked by alias); 25 Nov 2001 23:44:48 -0000
Mailing-List: contact gdb-patches-help@sourceware.cygnus.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 17117 invoked from network); 25 Nov 2001 23:44:47 -0000
Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35)
  by sourceware.cygnus.com with SMTP; 25 Nov 2001 23:44:47 -0000
Received: by zwingli.cygnus.com (Postfix, from userid 442)
	id 8BA615E9D8; Sun, 25 Nov 2001 18:46:03 -0500 (EST)
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: Doc fix for mn10300_analyze_prologue
Message-ID: <20011125234603.8BA615E9D8@zwingli.cygnus.com>
Date: Sun, 11 Nov 2001 08:58:00 -0000
X-SW-Source: 2001-11/txt/msg00218.txt.bz2
Message-ID: <20011111085800.54P84SPwBFCI5Uj-lmM1VMGl_7AxPH7JT-cZ6s6K4-Q@z>


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.