From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Hans-Peter Nilsson <hp@bitrange.com>,
Dimitrios Apostolou <jimis@gmx.net>, <gcc-patches@gcc.gnu.org>
Subject: Re: add strnlen to libiberty (was Re: Assembly output optimisations)
Date: Tue, 07 Aug 2012 15:07:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1208071459270.7298@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAKOQZ8z7Rua29G81P2qo-1M-LrQWXpvKgN7e0e1yzqzi38vsWw@mail.gmail.com>
On Tue, 7 Aug 2012, Ian Lance Taylor wrote:
> On Tue, Aug 7, 2012 at 2:30 AM, Hans-Peter Nilsson <hp@bitrange.com> wrote:
> >
> > Just don't forget that libiberty isn't a target library anymore.
> > To wit, the (GCC) run-time exception is moot for that code, AFAIK.
> > Maybe enough reason to abandon that rule so its code can be
> > truly and freely shared between GNU projects.
>
> The libiberty licensing is certainly confused. I just don't want to
> make it worse.
I think the natural way to sort it out is to move all the FSF-copyright
files therein (including include/) to GPLv3, no license exception, except
for cp-demangle.c (used in libstdc++-v3) and the headers it includes,
which should have the GCC Runtime Library Exception notice. libiberty is
a library for a limited number of GNU projects, all under GPLv3; as far as
I know the only reason it hasn't been converted to GPLv3 is that noone got
around to doing so. (gnulib also uses the practice of putting GPLv3
license notices on the files even if they are also available under other
licenses, with separate metadata indicating other licenses under which
files are available.)
That wouldn't sort out the question of what "This file is part of" notices
should be present, but would deal with the other license confusion.
(Ideally I think most of libiberty would be replaced by use of gnulib in
the projects using libiberty - I see no real advantage to the GNU Project
in having those two separate libraries for substantially the same purposes
- but that's a much larger and harder task, which would also involve, for
each libiberty file replaced by a gnulib version, ascertaining whether
there are any features or local changes in the libiberty version that
should be merged into the gnulib version or any common upstream such as
glibc. And some files in libiberty would probably need adding to gnulib
as part of such a project.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-08-07 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 0:19 Assembly output optimisations (was: PR 51094 - fprint_w() in output_addr_const() reinstated) Dimitrios Apostolou
2012-08-07 2:21 ` Hans-Peter Nilsson
2012-08-07 4:34 ` add strnlen to libiberty (was Re: Assembly output optimisations) Dimitrios Apostolou
2012-08-07 4:56 ` Ian Lance Taylor
2012-08-07 5:45 ` Dimitrios Apostolou
2012-08-07 6:25 ` Ian Lance Taylor
2012-08-07 9:30 ` Hans-Peter Nilsson
2012-08-07 13:45 ` Ian Lance Taylor
2012-08-07 15:07 ` Joseph S. Myers [this message]
2012-08-07 21:25 ` Assembly output optimisations (was: PR 51094 - fprint_w() in output_addr_const() reinstated) Dimitrios Apostolou
2012-08-07 22:43 ` Ian Lance Taylor
2012-08-07 23:28 ` Dimitrios Apostolou
2012-08-07 23:42 ` Ian Lance Taylor
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=Pine.LNX.4.64.1208071459270.7298@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=iant@google.com \
--cc=jimis@gmx.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).