From: Alan Modra <amodra@bigpond.net.au>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: objdump -M for x86
Date: Fri, 02 Nov 2001 15:12:00 -0000 [thread overview]
Message-ID: <20011114174350.K6922@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <3BF200F9.4070601@cygnus.com>; from ac131313@cygnus.com on Wed, Nov 14, 2001 at 12:28:25AM -0500
On Wed, Nov 14, 2001 at 12:28:25AM -0500, Andrew Cagney wrote:
> > Applying to mainline. Note to gdb people: Some backwards compatibility
> > stuff can be removed when i386-tdep.c and x86-64-tdep are updated to use
> > the new (old!) print_insn_i386.
>
> Hmm, I was wondering what you were talking about until I found this:
Actually, I was meaning that you don't need to call print_insn_i386_att
or ..._intel; Just call print_insn_i386 with info->mach set.
> (x86-64?)
Well, x86_64 follows the name used by -m
> Next problem ... If I understand things correctly, the set of possible
> options, for a given ISA family, is finite. Could that finite list be
> made available via a published interface?
Yes, good idea. Something like:
const char **opcodes_disasm_options (enum bfd_architecture arch)
returning a malloc'd list of strings for the given arch?
Alan
next prev parent reply other threads:[~2001-11-14 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011114134429.G6922@bubble.sa.bigpond.net.au>
2001-11-02 12:10 ` Andrew Cagney
2001-11-02 15:12 ` Alan Modra [this message]
2001-11-02 23:08 ` Andrew Cagney
2001-11-03 1:01 ` Alan Modra
2001-11-27 22:37 ` Andrew Cagney
2001-11-18 12:47 ` Andrew Cagney
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=20011114174350.K6922@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=ac131313@cygnus.com \
--cc=binutils@sources.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