From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27771 invoked by alias); 1 Feb 2002 20:44:57 -0000 Mailing-List: contact cgen-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sources.redhat.com Received: (qmail 27579 invoked from network); 1 Feb 2002 20:44:52 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 1 Feb 2002 20:44:52 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id EE87A3E02; Fri, 1 Feb 2002 15:44:44 -0500 (EST) Message-ID: <3C5AFE3C.6050405@cygnus.com> Date: Fri, 01 Feb 2002 12:44:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: "Frank Ch. Eigler" Cc: Andrew Cagney , binutils@sources.redhat.com, cgen@sources.redhat.com Subject: Re: include/dis-asm.h patch for cgen disassemblers References: <20020131162132.I19966@redhat.com> <3C59BD4A.9060900@cygnus.com> <20020131184230.A6166@redhat.com> <3C59DB61.3000106@cygnus.com> <20020131195734.D6166@redhat.com> <3C5A3694.7020502@cygnus.com> <20020201092827.H6166@redhat.com> <3C5AE910.4090009@cygnus.com> <20020201145627.A4226@redhat.com> <3C5AF43E.8030407@cygnus.com> <20020201151026.B4226@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q1/txt/msg00045.txt.bz2 > Hi - > > cagney wrote: > > >> > We did whatever must have seemed most useful at the time for their >> > treatment ... one bfd_arch, a bunch of bfd_mach's. Note that all >> > those coprocessors have a static set of instructions. > >> >> I'll take that as a royal we. I don't know what you did for the PS2 and >> will probably regret finding out. > > > It wasn't that bad. > > >> However, please expand. > > > In the context of discussing that port on a public mailing list, > and its iffy relevance to the current thread, I don't see why I > should do go into any more detail. You know where to find the > sources. I chose the PS2 because its architecture is public and, I think, it very much illustrates the underlying issue of the current discussion. The PS2 has a number of ISAs on a single chip. What is the correct way to define this from bfd? If you don't feel comfortable with answering this, then hopefully someone else will. Off the top of my head I can think of several ways: bfd_arch_mips bfd_mach_mips_ps2mips bfd_mach_mips_ps2video bfd_arch_ps2 bfd_mach_ps2mips bfd_mach_ps2video bfd_arch_mips bfd_mach_mips_ps2 bfd_arch_ps2video I think BFD to clearly document how this should be done, your isas is very much part of this. Andrew