Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix an unwinding problem on alpha-tru64
Date: Fri, 02 Apr 2004 23:01:00 -0000	[thread overview]
Message-ID: <406DF0D7.5060704@gnu.org> (raw)
In-Reply-To: <20040401003449.GY888@gnat.com>

Applied and committed, trunk and branch.

> Index: alpha-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/alpha-tdep.c,v
> retrieving revision 1.128
> diff -u -p -r1.128 alpha-tdep.c
> --- alpha-tdep.c	23 Mar 2004 14:47:54 -0000	1.128
> +++ alpha-tdep.c	31 Mar 2004 23:58:36 -0000
> @@ -1029,6 +1029,16 @@ alpha_heuristic_frame_unwind_cache (stru
>  	    {
>  	      reg = (word & 0x03e00000) >> 21;
>  
> +              /* Ignore this instruction if we have already encountered
> +                 an instruction saving the same register earlier in the
> +                 function code.  The current instruction does not tell
> +                 us where the original value upon function entry is saved.
> +                 All it says is that the function we are scanning reused
> +                 that register for some computation of its own, and is now
> +                 saving its result.  */
> +              if (info->saved_regs[reg])
> +                continue;
> +
>  	      if (reg == 31)
>  		continue;
>  

Andrew


  reply	other threads:[~2004-04-02 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  0:34 Joel Brobecker
2004-04-02 23:01 ` Andrew Cagney [this message]
2004-04-02 23:45   ` Joel Brobecker

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=406DF0D7.5060704@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.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