From: Mike Frysinger <vapier@gentoo.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb: clean up x86 cpuid implementations
Date: Wed, 19 Jun 2013 15:06:00 -0000 [thread overview]
Message-ID: <201306191053.51709.vapier@gentoo.org> (raw)
In-Reply-To: <51C1996E.1010001@redhat.com>
[-- Attachment #1: Type: Text/Plain, Size: 1696 bytes --]
On Wednesday 19 June 2013 07:43:42 Pedro Alves wrote:
> On 06/19/2013 03:46 AM, Mike Frysinger wrote:
> However, BTW, I failed to notice this before, but:
> > +++ b/gdb/common/i386-cpuid.h
> > @@ -0,0 +1,68 @@
> > +/*
> > + * Copyright (C) 2007-2013 Free Software Foundation, Inc.
> > + *
> > + * This file is free software; you can redistribute it and/or modify it
> > + * under the terms of the GNU General Public License as published by the
> > + * Free Software Foundation; either version 3, or (at your option) any
> > + * later version.
> > + *
> > + * This file is distributed in the hope that it will be useful, but
> > + * WITHOUT ANY WARRANTY; without even the implied warranty of
> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> > + * General Public License for more details.
> > + *
> > + * Under Section 7 of GPL version 3, you are granted additional
> > + * permissions described in the GCC Runtime Library Exception, version
> > + * 3.1, as published by the Free Software Foundation.
> > + *
> > + * You should have received a copy of the GNU General Public License and
> > + * a copy of the GCC Runtime Library Exception along with this program;
> > + * see the files COPYING3 and COPYING.RUNTIME respectively. If not, see
> > + * <http://www.gnu.org/licenses/>.
> > + */
>
> This header only contains gdb bits. I don't see a reason for making
> it GPL w/ runtime exception, rather than regular GPLv3+.
> Was it just a copy/paste?
from the top of the file:
/*
* Helper cpuid.h file copied from gcc-4.8.0. Code in gdb should not
* include this directly, but pull in i386-cpuid.h and use that func.
*/
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-19 14:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 18:51 [patch/rfc] " Mike Frysinger
2013-05-06 19:44 ` Eli Zaretskii
2013-05-06 20:30 ` Mike Frysinger
2013-05-07 2:41 ` Eli Zaretskii
2013-05-07 4:26 ` Doug Evans
2013-05-07 15:56 ` Eli Zaretskii
2013-05-07 13:29 ` [PATCH v2] " Mike Frysinger
2013-05-07 14:08 ` Pedro Alves
2013-05-07 14:19 ` Pedro Alves
2013-05-07 14:31 ` Mike Frysinger
2013-05-07 14:49 ` Pedro Alves
2013-05-07 15:05 ` Mike Frysinger
2013-05-07 15:21 ` Pedro Alves
2013-05-07 15:11 ` [PATCH v3] " Mike Frysinger
2013-06-17 6:16 ` Mike Frysinger
2013-06-17 17:52 ` Pedro Alves
2013-06-18 17:53 ` Mike Frysinger
2013-06-18 18:32 ` Pedro Alves
2013-06-18 23:37 ` Joel Brobecker
2013-06-19 3:12 ` Mike Frysinger
2013-06-19 12:11 ` Pedro Alves
2013-06-19 15:06 ` Mike Frysinger [this message]
2013-06-19 15:16 ` Pedro Alves
2013-06-19 15:50 ` Mike Frysinger
2013-06-19 16:59 ` Pedro Alves
2013-06-19 17:35 ` [PATCH v4] " Mike Frysinger
2013-06-19 17:42 ` Pedro Alves
2013-06-19 22:45 ` Mike Frysinger
2013-06-21 11:42 ` Regression for btrace [Re: [PATCH v4] gdb: clean up x86 cpuid implementations] Jan Kratochvil
2013-06-21 15:36 ` Mike Frysinger
2013-06-21 15:41 ` Pedro Alves
2013-06-21 15:51 ` [commit] " Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201306191053.51709.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox