From: "Stephen Done@home" <stephen.done@cw.com>
To: "Alan Lehotsky" <apl@alum.mit.edu>
Cc: <cgen@sources.redhat.com>
Subject: RE: Using CGEN Disassembler
Date: Wed, 21 Nov 2001 17:39:00 -0000 [thread overview]
Message-ID: <MOEKKPNMHCABCHMFENMEGEPJCEAA.stephen.done@cw.com> (raw)
Message-ID: <20011121173900.IJIw17QpLXBwFS7oWR2HsLBQBI0GclW9OFZrlgliPLg@z> (raw)
In-Reply-To: <p0433010bb8219b8ec6de@[192.168.1.254]>
Thanks everyone for your suggestions.
objdump is what I need, not cgen - I realise now.
Regs.
Steve
> -----Original Message-----
> From: Alan Lehotsky [ mailto:apl@alum.mit.edu ]
> Sent: 21 November 2001 18:00
> To: Stephen Done
> Cc: cgen@sources.redhat.com
> Subject: Re: Using CGEN Disassembler
>
>
> At 2:45 PM +0000 11/21/01, Stephen Done wrote:
>
> >I would like to use CGEN to disassemble some code for the Mitsubishi M32R
> >processor.
>
> Just get a binutils distribution and configure the m32r
> target and build.
>
> In the binutils build directory you'll find objdump - that
> does all the disassembly you could ever want...
>
> Or did you hope to build a disassembler into a tool YOU are
> building for yourself. (In which case, you still want
> to start with the objdump sources, as it shows how to call
> the cgen-generated routines for disassembly....
>
>
> >I have installed guile, and have downloaded the latest released
> version of
> >CGEN (1.0).
>
> You don't need any of that to build and run binutils - the
> cgen outputs are checked-in to the binutils tree (see
> the opcodes directory for the specifics....
>
> --
> ------------------------------------------------------------------------
>
> Quality Software Management
> http://home.earthlink.net/~qsmgmt
> apl@alum.mit.edu
> (978)287-0435 Voice
> (978)808-6836 Cell
> (978)287-0436 Fax
>
> Software Process Improvement and Management Consulting
> Language Design and Compiler Implementation
>
next prev parent reply other threads:[~2001-11-21 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 12:26 Stephen Done
2001-10-29 10:37 ` Greg McGary
2001-11-04 19:57 ` Stephen Done
2001-11-06 8:48 ` Greg McGary
2001-11-21 8:07 ` Greg McGary
2001-11-21 7:24 ` Stephen Done
2001-11-21 6:57 ` Greg McGary
2001-11-05 4:10 ` Frank Ch. Eigler
2001-11-05 17:03 ` Stephen Done
2001-11-21 7:54 ` Stephen Done
2001-11-21 7:46 ` Frank Ch. Eigler
2001-11-06 11:07 ` Alan Lehotsky
2001-11-06 10:48 ` Stephen Done at home [this message]
2001-11-21 17:39 ` Stephen Done@home
2001-11-23 6:35 ` Alan Lehotsky
2001-11-21 6:45 ` Stephen Done
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=MOEKKPNMHCABCHMFENMEGEPJCEAA.stephen.done@cw.com \
--to=stephen.done@cw.com \
--cc=apl@alum.mit.edu \
--cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).