From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19822 invoked by alias); 19 Jun 2013 15:55:47 -0000 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 Received: (qmail 19812 invoked by uid 89); 19 Jun 2013 15:55:47 -0000 X-Spam-SWARE-Status: No, score=-8.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 19 Jun 2013 15:55:47 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r5JFtjMP011845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Jun 2013 11:55:45 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r5JFthrZ009469; Wed, 19 Jun 2013 11:55:44 -0400 Message-ID: <51C1D47F.9080604@redhat.com> Date: Wed, 19 Jun 2013 16:59:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6 MIME-Version: 1.0 To: Mike Frysinger CC: gdb-patches@sourceware.org Subject: Re: [PATCH v3] gdb: clean up x86 cpuid implementations References: <201305061451.24861.vapier@gentoo.org> <201306191053.51709.vapier@gentoo.org> <51C1C8D5.5080809@redhat.com> <201306191120.52053.vapier@gentoo.org> In-Reply-To: <201306191120.52053.vapier@gentoo.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-06/txt/msg00498.txt.bz2 On 06/19/2013 04:20 PM, Mike Frysinger wrote: > technically, i386-cpuid.h was spawned from the gdb/testsuite/gdb.arch/i386- > cpuid.h which itself was spawned from the gcc sources (and both include the > exception) which is why the header was retained. > then again, FSF owns both, so if we want to drop that, it shouldn't be an > issue. doesn't matter to me either way. I'd rather make the GDB header plain GPLv3+. I find it simpler and least surprising if the header with the exception is only the verbatim(-ish) gcc imported header. Later on, if/when we want to move/add code to/from the GDB-specific header, we won't have to bother with this detail again. Thanks, -- Pedro Alves