Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [ppc64-linux]: skip linkage functions
Date: Fri, 06 Jun 2003 00:03:00 -0000	[thread overview]
Message-ID: <20030606000328.GA26538@nevyn.them.org> (raw)
In-Reply-To: <vt2fzmoxepa.fsf@zenia.home>

On Thu, Jun 05, 2003 at 06:54:57PM -0500, Jim Blandy wrote:
> 
> 2003-06-05  Jim Blandy  <jimb@redhat.com>
> 
> 	Recognize and skip 64-bit PowerPC Linux linkage functions.
> 	* ppc-linux-tdep.c (insn_d, insn_ds, insn_xfx, read_insn, struct
> 	insn_pattern, insns_match_pattern, d_field, ds_field): New
> 	functions, macros, and types for working with PPC instructions.
> 	(ppc64_standard_linkage, PPC64_STANDARD_LINKAGE_LEN,
> 	ppc64_in_solib_call_trampoline, ppc64_standard_linkage_target,
> 	ppc64_skip_trampoline_code): New functions, variables, and macros
> 	for recognizing and skipping linkage functions.
> 	(ppc_linux_init_abi): Use ppc64_in_solib_call_trampoline and
> 	ppc64_skip_trampoline_code for the 64-bit PowerPC Linux ABI.

Hmm.  Probably not good enough for our needs, but is the
DW_AT_trampoline attribute useful here?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-06-06  0:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 23:54 Jim Blandy
2003-06-06  0:03 ` Daniel Jacobowitz [this message]
2003-06-06  6:22   ` Jim Blandy
2003-06-06 13:11     ` Daniel Jacobowitz
2003-06-06 20:09       ` Jim Blandy
2003-06-06 20:17         ` Daniel Jacobowitz
2003-06-06 20:31           ` Jim Blandy
2003-06-06 21:40             ` Daniel Jacobowitz
2003-06-06 22:47               ` Jim Blandy
2003-06-10  0:05 ` Kevin Buettner
2003-06-10 17:29   ` 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=20030606000328.GA26538@nevyn.them.org \
    --to=drow@mvista.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