From: Kevin Buettner <kevinb@redhat.com>
To: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [ppc64-linux]: register CONVERT_FROM_FUNC_PTR_ADDR method
Date: Wed, 11 Jun 2003 22:42:00 -0000 [thread overview]
Message-ID: <1030611224249.ZM27163@localhost.localdomain> (raw)
In-Reply-To: Jim Blandy <jimb@redhat.com> "[ppc64-linux]: register CONVERT_FROM_FUNC_PTR_ADDR method" (Jun 11, 3:53am)
On Jun 11, 3:53am, Jim Blandy wrote:
> 2003-06-11 Jim Blandy <jimb@redhat.com>
>
> * ppc-linux-tdep.c (ppc64_linux_convert_from_func_ptr_addr): New
> function.
> (ppc_linux_init_abi): Register it as the
> CONVERT_FROM_FUNC_PTR_ADDR method under the PPC64 Linux ABI.
Okay, but could you revise the comment to not mention RS/6000 and
to make it clear that the representation in question only pertains
to the 64-bit ABI?
> + /* Support for CONVERT_FROM_FUNC_PTR_ADDR(ADDR).
> +
> + Usually a function pointer's representation is simply the address
> + of the function. On the RS/6000 however, a function pointer is
> + represented by a pointer to a TOC entry. This TOC entry contains
> + three words, the first word is the address of the function, the
> + second word is the TOC pointer (r2), and the third word is the
> + static chain value. Throughout GDB it is currently assumed that a
> + function pointer contains the address of the function, which is not
> + easy to fix. In addition, the conversion of a function address to
> + a function pointer would require allocation of a TOC entry in the
> + inferior's memory space, with all its drawbacks. To be able to
> + call C++ virtual methods in the inferior (which are called via
> + function pointers), find_function_addr uses this function to get the
> + function address from a function pointer. */
Kevin
next prev parent reply other threads:[~2003-06-11 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 8:52 Jim Blandy
2003-06-11 22:42 ` Kevin Buettner [this message]
2003-06-12 21:11 ` Jim Blandy
2003-06-12 21:44 ` Kevin Buettner
2003-06-13 4:48 ` Richard Henderson
2003-06-13 6:17 ` Kevin Buettner
2003-06-13 22:54 ` 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=1030611224249.ZM27163@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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