From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-38361-listarch-gdb-patches=sources.redhat.com@sources.redhat.com>
Received: (qmail 14533 invoked by alias); 8 Mar 2005 21:22:23 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.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 14244 invoked from network); 8 Mar 2005 21:22:15 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sourceware.org with SMTP; 8 Mar 2005 21:22:15 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j28LMFa0031200
	for <gdb-patches@sources.redhat.com>; Tue, 8 Mar 2005 16:22:15 -0500
Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j28LMDn10747;
	Tue, 8 Mar 2005 16:22:13 -0500
Received: from redhat.com (dhcp-172-16-25-137.sfbay.redhat.com [172.16.25.137])
	by potter.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id j28LM05s008477;
	Tue, 8 Mar 2005 16:22:02 -0500
Message-ID: <422E1777.6030602@redhat.com>
Date: Tue, 08 Mar 2005 21:22:00 -0000
From: Michael Snyder <msnyder@redhat.com>
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3) Gecko/20040924
MIME-Version: 1.0
To: David Anderson <davea@quasar.engr.sgi.com>
CC: gdb-patches@sources.redhat.com
Subject: Re: mn10300  commit, minor typo
References: <200503071605.j27G5kvu123792@quasar.engr.sgi.com>
In-Reply-To: <200503071605.j27G5kvu123792@quasar.engr.sgi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2005-03/txt/msg00124.txt.bz2

David Anderson wrote:
> mn10300-prologue.c
> +    MY_FRAME_IN_SP: The base of the current frame is actually in
> +    the stack pointer.  This can happen for frame pointerless
> +    functions, or cases where we're stopped in the prologue/epilogue
> +    itself.  For these cases mn10300_analyze_prologue will need up
> +    update fi->frame before returning or analyzing the register
> 
> 	'need up  update ' (see 2 lines above)  should be ... what?
> 
> +    save instructions.
> 

Probably "speed up".