From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30306 invoked by alias); 14 Nov 2001 09:38:10 -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 30253 invoked from network); 14 Nov 2001 09:38:08 -0000 Received: from unknown (HELO mailin3.email.bigpond.com) (139.134.6.34) by sourceware.cygnus.com with SMTP; 14 Nov 2001 09:38:08 -0000 Received: from bubble.local ([144.135.24.84]) by mailin3.email.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GMSB2C00.4H4 for ; Wed, 14 Nov 2001 19:44:36 +1000 Received: from 144.136.176.14 ([144.136.176.14]) by bwmam06.mailsvc.email.bigpond.com(MailRouter V2.9k 8368/8397630); 14 Nov 2001 19:37:55 Received: (qmail 19738 invoked by uid 179); 14 Nov 2001 09:37:54 -0000 Date: Sat, 03 Nov 2001 01:01: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: <20011114200754.M6922@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> <20011114174350.K6922@bubble.sa.bigpond.net.au> <3BF23030.4070201@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: <3BF23030.4070201@cygnus.com>; from ac131313@cygnus.com on Wed, Nov 14, 2001 at 03:49:52AM -0500 X-SW-Source: 2001-11/txt/msg00045.txt.bz2 On Wed, Nov 14, 2001 at 03:49:52AM -0500, Andrew Cagney wrote: > > > mode_64bit = (info->mach == bfd_mach_x86_64_intel_syntax > > || info->mach == bfd_mach_x86_64); > > > > + if (intel_syntax == -1) > > + intel_syntax = (info->mach == bfd_mach_i386_i386_intel_syntax > > + || info->mach == bfd_mach_x86_64_intel_syntax); > > + > > See my other e-mail. I can't find anything that sets ->mach to > .._intel_syntax so, apart from backward compatibility, I can't think of > a reason to hang on to those ``machine'' variants. I don't expect GDB > to start using them again. "objdump -d -m i386:intel" sets it via bfd_default_scan from the entry in bfd/cpu-i386.c > We'll need to do things like pin down the semantics. Which really means > agree on what something like ``x86-64 i386 i8086 intel att addr16 addr32 > data32 data16 suffix'' actually means, and ensure that GDB doesn't find > it has accepted a set of options only to find them later rejected by the > disasssembler. Perhaps the thing to do is add a function to bfd_arch_info_type that validates a -M string for the given arch. If a null string is passed in, it could return an array of possible string components. Alan