From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20373 invoked by alias); 18 Nov 2010 21:35:26 -0000 Received: (qmail 20234 invoked by uid 22791); 18 Nov 2010 21:35:26 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from caibbdcaaaaf.dreamhost.com (HELO homiemail-a59.g.dreamhost.com) (208.113.200.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Nov 2010 21:35:21 +0000 Received: from homiemail-a59.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTP id E1189564061; Thu, 18 Nov 2010 13:35:19 -0800 (PST) Received: from redwood.eagercon.com (c-67-188-213-237.hsd1.ca.comcast.net [67.188.213.237]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: eager@eagerm.com) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTPSA id AE34C56405C; Thu, 18 Nov 2010 13:35:19 -0800 (PST) Message-ID: <4CE59C16.6090906@eagerm.com> Date: Thu, 18 Nov 2010 21:35:00 -0000 From: Michael Eager User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: Pedro Alves CC: gdb-patches@sourceware.org, Joel Brobecker , Masaki Muranaka Subject: Re: [patch] target triplet for Microblaze. References: <201011181813.54314.pedro@codesourcery.com> <4CE57418.6010206@eagerm.com> <201011182045.04742.pedro@codesourcery.com> In-Reply-To: <201011182045.04742.pedro@codesourcery.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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/msg00247.txt.bz2 Pedro Alves wrote: > 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. Perhaps you are arguing that the patch should be rejected, so that the current behavior that only "microblaze-xilinx-gnu" would is accepted, and the change would make "microblaze-megacorp-gnu" also match. If so, then I agree that this would be an undesirable consequence. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077