From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1454 invoked by alias); 19 Aug 2002 22:40:05 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 1446 invoked from network); 19 Aug 2002 22:40:05 -0000 Received: from unknown (HELO dr-evil.shagadelic.org) (208.176.2.174) by sources.redhat.com with SMTP; 19 Aug 2002 22:40:05 -0000 Received: by dr-evil.shagadelic.org (Postfix, from userid 7518) id BADE59869; Mon, 19 Aug 2002 15:40:00 -0700 (PDT) Date: Mon, 19 Aug 2002 15:40:00 -0000 From: Jason R Thorpe To: Andrew Cagney Cc: Simon Posnjak , gdb-patches@sources.redhat.com Subject: Re: [PATCH] set osabi command Message-ID: <20020819154000.H2214@dr-evil.shagadelic.org> Mail-Followup-To: Jason R Thorpe , Andrew Cagney , Simon Posnjak , gdb-patches@sources.redhat.com References: <1029446386.30623.13.camel@klada.dyndns.org> <3D6171DA.7000100@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3D6171DA.7000100@ges.redhat.com>; from ac131313@ges.redhat.com on Mon, Aug 19, 2002 at 06:31:54PM -0400 Organization: Wasabi Systems, Inc. X-SW-Source: 2002-08/txt/msg00562.txt.bz2 On Mon, Aug 19, 2002 at 06:31:54PM -0400, Andrew Cagney wrote: > It gets complex though because the user could enter a sequence like: > > (gdb) set architecture arm > ... architecture forced to arm ... > (gdb) set osabi arm_eabi_v1 > ... osabi forced to arm_eabi_v1 > (gdb) set architecture mips > ... architecture forced to mips, what should happen to the OSABI? It > can't remain arm_eabi_v1 ... > > Idea's? * If it's e.g. "NetBSD/ELF", it's perfectly valid for ARM and MIPS, so it should stay the same. * Failing that, if the target triplet has a default OSABI, then that should be selected. * Failing that, the "unknown" OSABI. -- -- Jason R. Thorpe