Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/hppa] handle setting gp for calling shlib functions
Date: Thu, 29 Apr 2004 15:07:00 -0000	[thread overview]
Message-ID: <20040429150704.GZ3965@tausq.org> (raw)
In-Reply-To: <40910D4F.1020700@gnu.org>

> > static CORE_ADDR
> >+hppa32_convert_from_func_ptr_addr (struct gdbarch *gdbarch,
> >+				   CORE_ADDR addr,
> >+				   struct target_ops *targ)
> >+{
> >+  if (addr & 2)
> >+    {
> >+      ULONGEST gp;
> >+
> >+      addr &= ~3;
> >+
> >+      gp = read_memory_unsigned_integer (addr + 4, 4);
> >+      write_register (19, gp);
> >+      addr = read_memory_unsigned_integer (addr, 4);
> >+    }
> >+
> >+  return addr;
> >+}
> >+
> >+static CORE_ADDR
> 
> This should be using TARG methods read memory(2), and should not be 
> writing GP to register 19.

First point is understood, but about writing to register --

How else can this be handled? i.e. where else in the code path of
call_function_by_hand () will I be able to get ahold of the function
descriptor and set the gp? Unfortunately the func_addr that is passed
into push_dummy_call is already the canonicalized function address,
so i cannot do this as part of e.g. find_global_pointer.

thanks,
randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/


  reply	other threads:[~2004-04-29 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29  6:23 Randolph Chung
2004-04-29 14:12 ` Andrew Cagney
2004-04-29 15:07   ` Randolph Chung [this message]
2004-04-29 16:02     ` Andrew Cagney
2004-04-29 16:13       ` Randolph Chung
2004-04-29 16:48         ` Andrew Cagney
2004-04-30  4:04           ` Randolph Chung
2004-04-30 14:25             ` Andrew Cagney
2004-05-04 14:03               ` Andrew Cagney
2004-05-04 14:10                 ` Randolph Chung
2004-05-04 14:34                   ` Andrew Cagney

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=20040429150704.GZ3965@tausq.org \
    --to=randolph@tausq.org \
    --cc=cagney@gnu.org \
    --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