From: Daniel Jacobowitz <drow@false.org>
To: DJ Delorie <dj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add support for Renesas RX architecture
Date: Mon, 07 Dec 2009 21:29:00 -0000 [thread overview]
Message-ID: <20091207212849.GA455@caradoc.them.org> (raw)
In-Reply-To: <200912072120.nB7LKksp002963@greed.delorie.com>
On Mon, Dec 07, 2009 at 04:20:46PM -0500, DJ Delorie wrote:
>
> > Awesome! I've always wanted opcodes to do this.
>
> Look at opcodes/rx-decode.opc and opcodes/opc2c.c
>
> The simulator part is in src/sim/rx/rx.c
>
> The disassembler is somewhat trivial too, in opcodes/rx-dis.c, being
> all of 199 lines.
I took a look. It's a little opaque (I don't suppose there's
documentation on what opc2c does somewhere), but I get the drift.
Neat.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-12-07 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 23:19 Kevin Buettner
2009-12-04 17:38 ` Joel Brobecker
2009-12-07 20:39 ` Kevin Buettner
2009-12-07 20:56 ` Daniel Jacobowitz
2009-12-07 21:21 ` DJ Delorie
2009-12-07 21:29 ` Daniel Jacobowitz [this message]
2009-12-07 21:42 ` DJ Delorie
2009-12-07 22:36 ` Doug Evans
2009-12-07 23:20 ` DJ Delorie
2009-12-08 2:01 ` Doug Evans
2009-12-07 22:10 ` Michael Snyder
2009-12-07 22:38 ` Doug Evans
2009-12-07 20:00 ` Kevin Buettner
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=20091207212849.GA455@caradoc.them.org \
--to=drow@false.org \
--cc=dj@redhat.com \
--cc=gdb-patches@sourceware.org \
/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