Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: m.mueller99@kay-mueller.de
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: [RFC]: patch #2 for Sun C compiled target programs
Date: Thu, 24 Jun 2004 19:34:00 -0000	[thread overview]
Message-ID: <200406241934.i5OJYJS7017176@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <40D6F901.3010008@kay-mueller.de> (message from Michael Mueller on Mon, 21 Jun 2004 17:04:33 +0200)

   Date: Mon, 21 Jun 2004 17:04:33 +0200
   From: Michael Mueller <m.mueller99@kay-mueller.de>

   > 
   >    *** Problem 2 *************************************************
   > 
   >    Function sparc64_frame_base_address in sparc64-tdep.c needs to
   >    be fixed:
   > 
   >       /* ??? Should we take BIAS into account here?  */
   >       return cache->base;
   > 
   > 
   >    The answer to the question in comment is yes, see the appended patch.
   > 
   > That sounds reasonable.  I'll commit that bit if it works with
   > GCC/DWARF too.

   I debugged gcc3.4/dwarf. It does not call sparc64_frame_base_address. (I 
   assume dwarf uses a location expression of it's own to describe a fp 
   based address + BIAS as the location of a stack variable.)

Probably, yes.  I've committed the attached.

Thanks,

Mark


Index: ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>

	From Michael Mueller <m.mueller99@kay-mueller.de>:
	* sparc64-tdep.c (sparc64_frame_base_address): Take BIAS into
	account.

Index: sparc64-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/sparc64-tdep.c,v
retrieving revision 1.12
diff -u -p -r1.12 sparc64-tdep.c
--- sparc64-tdep.c 7 Jun 2004 02:02:55 -0000 1.12
+++ sparc64-tdep.c 24 Jun 2004 19:31:51 -0000
@@ -568,8 +568,7 @@ sparc64_frame_base_address (struct frame
   struct sparc_frame_cache *cache =
     sparc64_frame_cache (next_frame, this_cache);
 
-  /* ??? Should we take BIAS into account here?  */
-  return cache->base;
+  return cache->base + BIAS;
 }
 
 static const struct frame_base sparc64_frame_base =


  reply	other threads:[~2004-06-24 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 17:21 Michael Mueller
2004-06-18 21:59 ` Mark Kettenis
2004-06-21 15:05   ` Michael Mueller
2004-06-24 19:34     ` Mark Kettenis [this message]
2004-06-24 19:47     ` Mark Kettenis
2004-06-24 20:57       ` Michael Mueller
2004-06-28  8:16       ` Michael Mueller

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=200406241934.i5OJYJS7017176@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=m.mueller99@kay-mueller.de \
    /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