Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Duffek <nsd@redhat.com>
To: jimb@cygnus.com
Cc: ezannoni@cygnus.com, gdb-patches@sources.redhat.com, taylor@candd.org
Subject: Re: [RFA] findvar.c: support LOC_BASEREG[_ARG] on Harvard archs
Date: Mon, 16 Jul 2001 14:35:00 -0000	[thread overview]
Message-ID: <200107161954.f6GJskB20239@rtl.cygnus.com> (raw)
In-Reply-To: <np7kx8zpy0.fsf@zwingli.cygnus.com>

On 16-Jul-2001, Jim Blandy wrote:

>The alternative would be to have that code call
>value_from_register and then value_as_pointer, as is done for
>LOC_REGPARM_ADDR, rather than banging the bits yourself with
>get_saved_register and extract_address.

Okay, here's an updated patch that uses value_from_register and
value_as_pointer.

>But if you are going to bang
>the bits yourself, you do need to call POINTER_TO_ADDRESS.

I don't think there's any applicable bit-banging here.

>You should do similar things for LOC_INDIRECT,

Aren't LOC_INDIRECT addresses from the symbol table and therefore already
Harvard-adjusted?

>LOC_REF_ARG,

I think that architectures already handle this in their own
FRAME_ARGS_ADDRESS implementations, so this would do double pointer
translation.

>LOC_THREAD_LOCAL_STATIC.

Agreed.  In fact, the code for LOC_THREAD_LOCAL_STATIC is identical to
that for LOC_BASEREG_ARG, so I've just moved LOC_THREAD_LOCAL_STATIC to
the LOC_BASEREG_ARG case in the appended patch.

Nick

Index: gdb/findvar.c
===================================================================
diff -up gdb/findvar.c gdb/findvar.c
--- gdb/findvar.c	Mon Jul 16 15:52:10 2001
+++ gdb/findvar.c	Mon Jul 16 15:51:58 2001
@@ -610,22 +610,15 @@ addresses have not been bound by the dyn
 
     case LOC_BASEREG:
     case LOC_BASEREG_ARG:
-      {
-	char *buf = (char*) alloca (MAX_REGISTER_RAW_SIZE);
-	get_saved_register (buf, NULL, NULL, frame, SYMBOL_BASEREG (var),
-			    NULL);
-	addr = extract_address (buf, REGISTER_RAW_SIZE (SYMBOL_BASEREG (var)));
-	addr += SYMBOL_VALUE (var);
-	break;
-      }
-
     case LOC_THREAD_LOCAL_STATIC:
       {
-	char *buf = (char*) alloca (MAX_REGISTER_RAW_SIZE);
+	value_ptr regval;
 
-	get_saved_register (buf, NULL, NULL, frame, SYMBOL_BASEREG (var),
-			    NULL);
-	addr = extract_address (buf, REGISTER_RAW_SIZE (SYMBOL_BASEREG (var)));
+	regval = value_from_register (lookup_pointer_type (type),
+				      SYMBOL_BASEREG (var), frame);
+	if (regval == NULL)
+	  error ("Value of base register not available.");
+	addr = value_as_pointer (regval);
 	addr += SYMBOL_VALUE (var);
 	break;
       }


  reply	other threads:[~2001-07-16 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 10:13 Nick Duffek
2001-07-16 11:29 ` Jim Blandy
2001-07-16 14:35   ` Nick Duffek [this message]
     [not found]     ` <npsnfwy0u8.fsf@zwingli.cygnus.com>
2001-07-16 15:49       ` Andrew Cagney
2001-07-16 15:59         ` Jim Blandy
2001-07-16 16:13         ` Nick Duffek
2001-07-16 15:59       ` Nick Duffek
2001-07-16 16:09         ` Andrew Cagney
2001-07-16 16:13           ` Nick Duffek
2001-07-16 16:17           ` Nick Duffek
     [not found] ` <3B535097.5040106@cygnus.com>
2001-07-16 14:16   ` Jim Blandy

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=200107161954.f6GJskB20239@rtl.cygnus.com \
    --to=nsd@redhat.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@cygnus.com \
    --cc=taylor@candd.org \
    /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