From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-67008-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 20557 invoked by alias); 18 Sep 2009 16:45:48 -0000
Received: (qmail 20546 invoked by uid 22791); 18 Sep 2009 16:45:47 -0000
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 18 Sep 2009 16:45:43 +0000
Received: (qmail 18514 invoked from network); 18 Sep 2009 16:45:41 -0000
Received: from unknown (HELO orlando) (pedro@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 18 Sep 2009 16:45:41 -0000
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Check solib bfd arch
Date: Fri, 18 Sep 2009 16:45:00 -0000
User-Agent: KMail/1.9.10
Cc: Daniel Jacobowitz <drow@false.org>,  Ulrich Weigand <uweigand@de.ibm.com>,  Mark Kettenis <mark.kettenis@xs4all.nl>,  brobecker@adacore.com,  teawater@gmail.com,  msnyder@vmware.com
References: <200909181553.45603.pedro@codesourcery.com> <20090918162511.GA25315@caradoc.them.org> <200909181741.43702.pedro@codesourcery.com>
In-Reply-To: <200909181741.43702.pedro@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain;   charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200909181746.03956.pedro@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-09/txt/msg00603.txt.bz2

On Friday 18 September 2009 17:41:43, Pedro Alves wrote:
> I think that's the same in practice as Joel's original
> patch then, since `compatible' either returns either
> NULL, a or b. =A0This still catches the
> obviously-incompatible cases, so may be worth keeping,
> while anything smarter is probably not worth the effort
> then.
>=20

Grrrr...

     Some targets (e.g. MIPS as of 2006-12-04) don't fully
     implement this, instead always returning NULL or the first
     argument.  We detect that case by checking both directions.  */

  compat1 =3D selected->compatible (selected, from_target);
  compat2 =3D from_target->compatible (from_target, selected);

--=20
Pedro Alves