From: Hans-Peter Nilsson <hp@bitrange.com>
To: Ian Lance Taylor <iant@google.com>
Cc: 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 09:30:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.00.1208070524050.28450@dair.pair.com> (raw)
In-Reply-To: <CAKOQZ8zNTTpR2-TXBXTzQkPxO5EyKs=wqyshvPvfPGYgM3Qu0Q@mail.gmail.com>
On Mon, 6 Aug 2012, Ian Lance Taylor wrote:
> On Mon, Aug 6, 2012 at 10:44 PM, Dimitrios Apostolou <jimis@gmx.net> wrote:
> >
> > What else is missing to make this patch appropriate for libiberty? Should I
> > change the prolog in strnlen.c, since I only copied it intact from gnulib?
>
> We generally try to avoid straight GPL source code without runtime
> exception in libiberty, and I don't see a reason to bend that rule for
> this trivial function.
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.
brgds, H-P
next prev parent reply other threads:[~2012-08-07 9:30 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 [this message]
2012-08-07 13:45 ` Ian Lance Taylor
2012-08-07 15:07 ` Joseph S. Myers
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=alpine.BSF.2.00.1208070524050.28450@dair.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--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).