From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30961 invoked by alias); 18 Nov 2010 18:14:06 -0000 Received: (qmail 30951 invoked by uid 22791); 18 Nov 2010 18:14:05 -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 18:14:01 +0000 Received: (qmail 20379 invoked from network); 18 Nov 2010 18:13:59 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Nov 2010 18:13:59 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [patch] target triplet for Microblaze. Date: Thu, 18 Nov 2010 18:14: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: <20101118171030.GA2634@adacore.com> <4CE565D6.1010009@eagerm.com> In-Reply-To: <4CE565D6.1010009@eagerm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201011181813.54314.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/msg00243.txt.bz2 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. -- Pedro Alves