Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [obish]  Add target to convert_from_func_ptr_addr
Date: Wed, 22 Oct 2003 23:36:00 -0000	[thread overview]
Message-ID: <3F97147B.9020104@redhat.com> (raw)
In-Reply-To: <3F955812.7000106@redhat.com>

> Hello,
> 
> This patch simply makes the implicit "struct target_ops" parameter to convert_from_func_ptr_addr explicit (it also makes it pure multi-arch).  It doesn't try to update any actual architecture code so I think this is pretty save and will commit in a few hours (after my cross builds finish).
> 
> By doing this, the new architecture bfd_entry_point previous proposed in:
> 
> [ppc64-linux] gdbarch hook to find true execution entry point
> http://sources.redhat.com/ml/gdb-patches/2003-06/msg00362.html
> [ppc64-linux]: correctly find a BFD's code entry point address
> http://sources.redhat.com/ml/gdb-patches/2003-06/msg00437.html
> 
> made entirely redundant.  ya!

I've checked this in.

Andrew


> 2003-10-21  Andrew Cagney  <cagney@redhat.com>
> 
> 	* gdbarch.sh (convert_from_func_ptr_addr): Convert to a pure
> 	multi-arch method, add "targ" parameter.
> 	(struct target_ops): Declare.	
> 	* gdbarch.h, gdbarch.c: Re-generate.
> 	* Makefile.in (c-valprint.o): Update dependencies.
> 	* arch-utils.h: Update copyright.
> 	(convert_from_func_ptr_addr_identity): Declare.
> 	* arch-utils.c (convert_from_func_ptr_addr_identity): New function.
> 	* rs6000-tdep.c (rs6000_convert_from_func_ptr_addr): Upate.
> 	* ppc-linux-tdep.c (ppc64_linux_convert_from_func_ptr_addr): Update.
> 	* infcall.c (find_function_addr, call_function_by_hand): Update.
> 	* c-valprint.c: Include "target.h".
> 	(print_function_pointer_address): Update.
> 	



      reply	other threads:[~2003-10-22 23:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 16:00 Andrew Cagney
2003-10-22 23:36 ` Andrew Cagney [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=3F97147B.9020104@redhat.com \
    --to=ac131313@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