From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa:rs6000] Framefy rs6000 (and GNU/Linux PPC)
Date: Sat, 20 Mar 2004 05:03:00 -0000 [thread overview]
Message-ID: <20040319220322.418ac90b@saguaro> (raw)
In-Reply-To: <40428F53.5080502@gnu.org>
On Sun, 29 Feb 2004 20:18:11 -0500
Andrew Cagney <cagney@gnu.org> wrote:
> * ppc-linux-tdep.c: Include "trad-frame.h", and "frame-unwind.h".
> Update copyright.
> (struct ppc_linux_sigtramp_cache, ppc_linux_sigtramp_cache)
> (ppc_linux_sigtramp_this_id, ppc_linux_sigtramp_prev_register)
> (ppc_linux_sigtramp_unwind, ppc_linux_sigtramp_sniffer)
> (ppc_linux_init_abi): Add both 32- and 64-bit signal trampoline
> unwinders. #ifdef legacy frame code.
> * rs6000-tdep.c: Include "trad-frame.h", "frame-unwind.h", and
> "frame-base.h".
> (rs6000_unwind_pc, rs6000_unwind_dummy_id)
> (struct rs6000_frame_cache, rs6000_frame_cache)
> (rs6000_frame_this_id, rs6000_frame_prev_register)
> (rs6000_frame_sniffer, rs6000_frame_unwind)
> (rs6000_frame_base_address, rs6000_frame_base_sniffer)
> (rs6000_frame_base): Implement a traditional frame unwinder.
> (rs6000_gdbarch_init): When unknown, NetBSD, or GNU/Linux use the
> frame unwinder.
I've checked these changes in. I've also followed up with my own patch
(which I'll post separately) which enables the new frame management
code for AIX and deletes the old frame management code.
Kevin
prev parent reply other threads:[~2004-03-20 5:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 1:18 Andrew Cagney
2004-03-02 23:01 ` Kevin Buettner
2004-03-19 0:09 ` Kevin Buettner
2004-03-19 0:09 ` Andrew Cagney
2004-03-03 15:36 ` Andrew Cagney
2004-03-15 18:28 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Kevin Buettner
2004-03-15 20:15 ` Kevin Buettner
2004-03-19 0:09 ` Andrew Cagney
2004-03-15 22:51 ` Andrew Cagney
2004-03-16 15:56 ` Kevin Buettner
2004-03-19 0:09 ` Kevin Buettner
2004-03-19 0:09 ` Andrew Cagney
2004-03-20 5:03 ` Kevin Buettner [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=20040319220322.418ac90b@saguaro \
--to=kevinb@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