From: Jim Blandy <jimb@redhat.com>
To: gdb@sources.redhat.com
Subject: GDB 6.2 E500 branch created
Date: Wed, 08 Sep 2004 15:45:00 -0000 [thread overview]
Message-ID: <vt2wtz49351.fsf@zenia.home> (raw)
I've created a branch off the GDB 6.2 release that holds the current
status of my work on native PowerPC E500 Linux, with support for the
Signal Processing Extension (SPE) APU. To check out the branch, login
to the repository following the instructions available on:
http://sources.redhat.com/gdb/current/
And then check out the branch jimb-gdb_6_2-e500-branch like this:
cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src co -r jimb-gdb_6_2-e500-branch gdb+dejagnu
Then you can configure and build this system on a native PowerPC E500
Linux system in the normal way.
This branch includes the following changes that are not currently
present in the GDB trunk, because they are awaiting review or
revision:
- Support for variables allocated to all 64 bits of the gprs
(partial, architecture-specific support for DW_OP_piece)
- Support for reading SPE registers in multi-threaded programs
(support for the libthread_db xregs functions; this requires an
appropriately patched GNU C library, which will be available soon)
- Support for Dwarf 2 CFI for PowerPC targets.
reply other threads:[~2004-09-08 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vt2wtz49351.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=gdb@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