From: Orjan Friberg <orjan.friberg@axis.com>
To: gdb-patches@sources.redhat.com
Subject: [regformats/rfa] CRIS/CRISv32 gdbserver support (part 1)
Date: Fri, 14 Jan 2005 09:52:00 -0000 [thread overview]
Message-ID: <41E7965D.503@axis.com> (raw)
Hot on the heels of the gdbserver watchpoint patch (at
http://sources.redhat.com/ml/gdb-patches/2005-01/msg00081.html) and the submit
of the CRISv32 port, here comes part 1 of the necessary pieces for building a
gdbserver for CRIS and CRISv32. (Any fallout from the watchpoint or gdb patch
will of course be incorporated into this if necessary before committing.)
The regformats and gdbserver patches are split into two to make it more
manageable. This first part in particular is probably not very interesting.
Ok to commit?
2005-01-15 Orjan Friberg <orjanf@axis.com>
* regformats/reg-cris.dat: New file with register definitions for CRIS.
* regformats/reg-crisv32.dat: Ditto for CRISv32.
New file reg-cris.dat:
name:cris
expedite:r8,sp,pc
32:r0
32:r1
32:r2
32:r3
32:r4
32:r5
32:r6
32:r7
32:r8
32:r9
32:r10
32:r11
32:r12
32:r13
32:sp
32:pc
8:p0
8:vr
0:p2
0:p3
16:p4
16:ccr
0:p6
32:mof
32:p8
32:ibr
32:irp
32:srp
32:bar
32:dccr
32:brp
32:usp
New file reg-crisv32.dat:
name:cris
expedite:r8,sp,pc
32:r0
32:r1
32:r2
32:r3
32:r4
32:r5
32:r6
32:r7
32:r8
32:r9
32:r10
32:r11
32:r12
32:r13
32:sp
32:acr
8:bz
8:vr
32:pid
8:srs
16:wz
32:exs
32:eda
32:mof
32:dz
32:ebp
32:erp
32:srp
32:nrp
32:ccs
32:usp
32:spc
32:pc
32:s0
32:s1
32:s2
32:s3
32:s4
32:s5
32:s6
32:s7
32:s8
32:s9
32:s10
32:s11
32:s12
32:s13
32:s14
32:s15
--
Orjan Friberg
Axis Communications
next reply other threads:[~2005-01-14 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 9:52 Orjan Friberg [this message]
2005-01-30 4:42 ` Daniel Jacobowitz
2005-02-01 14:26 ` Orjan Friberg
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=41E7965D.503@axis.com \
--to=orjan.friberg@axis.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