From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5308 invoked by alias); 14 Nov 2001 07:14:02 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5257 invoked from network); 14 Nov 2001 07:13:58 -0000 Received: from unknown (HELO mta01ps.bigpond.com) (144.135.25.133) by sourceware.cygnus.com with SMTP; 14 Nov 2001 07:13:58 -0000 Received: from bubble.local ([144.135.25.84]) by mta01ps.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GMS4E800.4K9 for ; Wed, 14 Nov 2001 17:20:32 +1000 Received: from 144.136.176.14 ([144.136.176.14]) by psmam06.mailsvc.email.bigpond.com(MailRouter V2.9k 8425/5982555); 14 Nov 2001 17:13:50 Received: (qmail 19491 invoked by uid 179); 14 Nov 2001 07:13:50 -0000 Date: Fri, 02 Nov 2001 15:12:00 -0000 From: Alan Modra To: Andrew Cagney Cc: binutils@sources.redhat.com, gdb@sources.redhat.com Subject: Re: objdump -M for x86 Message-ID: <20011114174350.K6922@bubble.sa.bigpond.net.au> Mail-Followup-To: Andrew Cagney , binutils@sources.redhat.com, gdb@sources.redhat.com References: <20011114134429.G6922@bubble.sa.bigpond.net.au> <3BF200F9.4070601@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i In-Reply-To: <3BF200F9.4070601@cygnus.com>; from ac131313@cygnus.com on Wed, Nov 14, 2001 at 12:28:25AM -0500 X-SW-Source: 2001-11/txt/msg00042.txt.bz2 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