From: Andrew Cagney <ac131313@cygnus.com>
To: Jiri Smid <smid@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Misc; Was: [RFA]: x86_64 target files
Date: Thu, 30 Aug 2001 07:39:00 -0000 [thread overview]
Message-ID: <3B8E5021.2070209@cygnus.com> (raw)
In-Reply-To: <s8v7kvmgd2g.fsf@naga.suse.cz>
>> Have a look at the ARM which queries opcodes for a list of disassembly variants
>> instead of duplicating those variants here.
>>
>
> I have looked at ARM and there is list of dissassembly flavors
> (register set names) obtained from binutils. But in i386/x86_64 case there
> is no way how to get list of flavors. I am not sure what do you mean...
> Changes in binutils?
Hmm, the interface isn't as clean as I remembered :-). Yes, it would
mean getting a change into binutils.
The theory is that GDB knows nothing about the assembler except how to
call it. It defers to opcodes for things like assembler flavour names -
this guarentees that objdump and GDB have a consistent interface. For
you, it is looking like the best thing is to file a PR and follow it up
later.
One side thought, I'm surprised that there isn't a simple ``set
disassembler ...'' command.
Andrew
next prev parent reply other threads:[~2001-08-30 7:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 7:20 Jiri Smid
2001-08-02 8:39 ` Eli Zaretskii
2001-08-02 9:37 ` Andreas Jaeger
2001-08-02 9:43 ` Kevin Buettner
2001-08-09 22:53 ` Andrew Cagney
2001-08-09 23:12 ` config/i386/xm-x86_64.h; Was " Andrew Cagney
2001-08-09 23:25 ` configure.host; Was: " Andrew Cagney
2001-08-09 23:41 ` configure.tgt; " Andrew Cagney
2001-08-09 23:57 ` Misc; " Andrew Cagney
2001-08-30 1:35 ` Jiri Smid
2001-08-30 7:39 ` Andrew Cagney [this message]
2001-08-30 11:03 ` Andreas Jaeger
2001-08-30 16:53 ` Andrew Cagney
2001-08-31 0:13 ` Andreas Jaeger
2001-08-31 2:00 ` i386 flavors [Was: Re: Misc; Was: [RFA]: x86_64 target files] Andreas Jaeger
2001-08-31 10:39 ` Misc; Was: [RFA]: x86_64 target files Andrew Cagney
2001-08-31 13:12 ` Andreas Jaeger
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=3B8E5021.2070209@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=smid@suse.cz \
/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