From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-13921-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 20548 invoked by alias); 22 May 2003 22:53:29 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 16652 invoked from network); 22 May 2003 22:51:46 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sources.redhat.com with SMTP; 22 May 2003 22:51:46 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h4MMpkH06691
	for <gdb@sources.redhat.com>; Thu, 22 May 2003 18:51:46 -0400
Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4MMpkI11467;
	Thu, 22 May 2003 18:51:46 -0400
Received: from localhost.localdomain (vpn50-3.rdu.redhat.com [172.16.50.3])
	by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4MMpjo04344;
	Thu, 22 May 2003 18:51:46 -0400
Received: (from kev@localhost)
	by localhost.localdomain (8.11.6/8.11.6) id h4MMpeo31669;
	Thu, 22 May 2003 15:51:40 -0700
Date: Thu, 22 May 2003 22:53:00 -0000
From: Kevin Buettner <kevinb@redhat.com>
Message-Id: <1030522225139.ZM31668@localhost.localdomain>
In-Reply-To: Kumar Gala <kumar.gala@motorola.com>
        "disassembly in gdb?" (May 22,  5:24pm)
References: <224A48FA-8CA4-11D7-B5D0-000393DBC2E8@motorola.com>
To: Kumar Gala <kumar.gala@motorola.com>, <gdb@sources.redhat.com>
Subject: Re: disassembly in gdb?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2003-05/txt/msg00304.txt.bz2

On May 22,  5:24pm, Kumar Gala wrote:

> How does gdb know which disassembler options to use for a given 
> architecture target?  For example on PPC there are various flags to 
> enable such things as SPE, AltiVec, ISEL, etc.
> 
> Is there anyway in an existing gdb to have the disassembler understand 
> a different subset of opcodes for the architecture?

This is supposed to be handled by the disassembler_options field in
the disassemble_info struct.  Unfortunately, I don't see anything
in the public GDB sources which set these options for any of the
PPC cores.  (mips and i386 have some code which do this though.)

Kevin