Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gcc-patches@gcc.gnu.org,
	Binutils Development <binutils@sourceware.org>,
	        gdb-patches@sourceware.org
Subject: Re: Patch: merge src and gcc copies of dwarf2.h
Date: Sat, 20 Jun 2009 07:17:00 -0000	[thread overview]
Message-ID: <m3vdmridce.fsf@google.com> (raw)
In-Reply-To: <m37hz8rksr.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri\, 19 Jun 2009 15\:11\:16 -0600")

Tom Tromey <tromey@redhat.com> writes:

> * Files in include/ are still GPLv2.
>   I made the new dwarf2.h GPLv3, but GCC's copy has the exception text
>   as well.

I believe the file in include/ should also have the exception text.  The
question to ask is: might a plugin want to include this file?  If yes,
it should have the exception text.


> * gcc's dwarf2.h defines INTERNAL_DW_OP_tls_addr.
>   I left this in there, but IMO it is somewhat of a hack.
>   Perhaps it should be local to gcc, like:
>
>     #define INTERNAL_DW_OP_tls_addr (enum dwarf_location_atom) 0x103

That would not work reliably in C++ since it would be out of range of
the other enum values.

>   Or maybe be made an explicit flag somewhere instead of abusing an
>   enum.

That would be fine.


> Bootstrapped and regtested on x86-64 (compile farm).
> Ok?  And for src, assuming that there are no regressions?

This is OK for gcc if you use the exception text in the license.

Thanks.

Ian


  reply	other threads:[~2009-06-20  7:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 21:11 Tom Tromey
2009-06-20  7:17 ` Ian Lance Taylor [this message]
2009-06-29 18:13   ` Tom Tromey
2009-06-29 20:00     ` Ian Lance Taylor
2009-06-29 23:59       ` Tom Tromey
2009-06-30 19:51         ` Jakub Jelinek
2009-06-30 20:03           ` Tom Tromey
2009-07-01 21:57             ` Tom Tromey
2009-07-02  0:30               ` Ian Lance Taylor
2009-07-02 17:30                 ` Tom Tromey
2009-07-09 20:32                 ` Tom Tromey

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=m3vdmridce.fsf@google.com \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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