From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15463 invoked by alias); 24 Oct 2003 00:38:17 -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 15455 invoked from network); 24 Oct 2003 00:38:16 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 24 Oct 2003 00:38:16 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 587422B89; Thu, 23 Oct 2003 20:38:17 -0400 (EDT) Message-ID: <3F987479.7020904@redhat.com> Date: Fri, 24 Oct 2003 00:38:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [patch/rfc,rfa:ppc64] Add osabi wildcard support References: <3F986371.9060708@redhat.com> <20031023234150.GA16173@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-10/txt/msg00714.txt.bz2 > > The table is almost certainly not complete, but that's not the problem > here. The e500 is compatible with ppc - the e500 can run ppc code. > Vice versa is not necessarily true. There's a FIXME in osabi.c saying > that we should look for the most compatible architecture: FYI, the e500 doesn't have the PPC's FPU so it can't (well ignoring emulation) run PPC floating-point code. Andrew