From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29432 invoked by alias); 18 Nov 2010 20:45:17 -0000 Received: (qmail 29420 invoked by uid 22791); 18 Nov 2010 20:45:16 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Nov 2010 20:45:09 +0000 Received: (qmail 19857 invoked from network); 18 Nov 2010 20:45:07 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Nov 2010 20:45:07 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [patch] target triplet for Microblaze. Date: Thu, 18 Nov 2010 20:45:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.33-29-realtime; KDE/4.4.5; x86_64; ; ) Cc: Michael Eager , Joel Brobecker , Masaki Muranaka References: <201011181813.54314.pedro@codesourcery.com> <4CE57418.6010206@eagerm.com> In-Reply-To: <4CE57418.6010206@eagerm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201011182045.04742.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-11/txt/msg00245.txt.bz2 On Thursday 18 November 2010 18:44:40, Michael Eager wrote: > Pedro Alves wrote: > > On Thursday 18 November 2010 17:43:50, Michael Eager wrote: > > > >> MicroBlaze is a proprietary processor developed by Xilinx and, AFAIK, > >> they have not licensed it to other manufacturers. > > > > > > > >> Xilinx is the only possible specification which meets the definition > >> in Autobook. > > > > That can't be right. > > > > " cpu > > The type of processor used on the system. (...) > > > > manufacturer > > A somewhat freeform field which indicates the manufacturer of the system. (...)" > > > > It's manufacturer of the system, not of the CPU. > > Note "used on the system", therefore cpu != system. And "system" > > is really a broad term. AFAIK, it's really a freeform field in > > practice, so you should be able to put anything there. For example, > > if one takes xilink's toolchain sources (the gpl bits), fork / patch > > them for some reason, and build / distribute them oneself, one > > might want to legitimately change the manufacturer field to > > avoid confusion. > > System, in this case, is the FPGA, manufactured by Xilinx. Or "system" is a board that includes an FPGA manufactured by Xilinx, yet assembled and sold by some other vendor, that happens to decide to add some spice or to do some incompatible changes to Xilink's version of the toolchain. In the case of an intel x86 cpu, what you call the "system"? That answer to that should reveal that your interpretation of system cannot be the only one possible. A recent somewhat related example of this is the addition of the w64 vendor to distinguish the mingw-w64 toolchain from the mingw.org (vendor == pc) toolchain. Quoting the whole description this time: "manufacturer A somewhat freeform field which indicates the manufacturer of the system. This is often simply `unknown'. Other common strings are `pc' for an IBM PC compatible system, or the name of a workstation vendor, such as `sun'. " Emphasis on "somewhat freeform". -- Pedro Alves