Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fred Fish <fnf@ninemoons.com>
To: Elena Zannoni <ezannoni@redhat.com>, fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Eliminate useless test of variable before overwriting it in sh-tdep.c
Date: Fri, 20 Feb 2004 00:17:00 -0000	[thread overview]
Message-ID: <200402191717.18292.fnf@ninemoons.com> (raw)
In-Reply-To: <16432.58684.128094.521393@localhost.redhat.com>

On Monday 16 February 2004 08:43, Elena Zannoni wrote:
>
> ok.

Committed.

-Fred

2004-02-19  Fred Fish  <fnf@redhat.com>

	* sh-tdep.c (sh_analyze_prologue): Eliminate useless test of
	cache->uses_fp prior to setting it.

Index: sh-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/sh-tdep.c,v
retrieving revision 1.164
diff -c -p -r1.164 sh-tdep.c
*** sh-tdep.c	19 Feb 2004 23:05:07 -0000	1.164
--- sh-tdep.c	20 Feb 2004 00:14:57 -0000
*************** sh_analyze_prologue (CORE_ADDR pc, CORE_
*** 482,489 ****
  	}
        else if (IS_MOV_SP_FP (inst))
  	{
! 	  if (!cache->uses_fp)
! 	    cache->uses_fp = 1;
  	  /* At this point, only allow argument register moves to other
  	     registers or argument register moves to @(X,fp) which are
  	     moving the register arguments onto the stack area allocated
--- 482,488 ----
  	}
        else if (IS_MOV_SP_FP (inst))
  	{
! 	  cache->uses_fp = 1;
  	  /* At this point, only allow argument register moves to other
  	     registers or argument register moves to @(X,fp) which are
  	     moving the register arguments onto the stack area allocated



      reply	other threads:[~2004-02-20  0:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 22:12 Fred Fish
2004-02-16 15:48 ` Elena Zannoni
2004-02-20  0:17   ` Fred Fish [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200402191717.18292.fnf@ninemoons.com \
    --to=fnf@ninemoons.com \
    --cc=ezannoni@redhat.com \
    --cc=fnf@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox