public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Carlos O'Donell <carlos@redhat.com>,
	Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Dynamic growable arrays for internal use
Date: Thu, 01 Jun 2017 18:08:00 -0000	[thread overview]
Message-ID: <91d54a00-2c61-52a8-76d6-3d035f1acfd5@cs.ucla.edu> (raw)
In-Reply-To: <4ed5035d-3b88-0030-b3b4-b7e4e2e13e88@redhat.com>

On 06/01/2017 09:13 AM, Carlos O'Donell wrote:
>> http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/xalloc.h  
>> http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/xmalloc.c
> Before I look...
>
> What license do these files have?

They're GPLed, with copyright assigned to the FSF. Although we haven't 
run into a need for an LGPLed version, that would not be hard to 
arrange, so I wouldn't worry about the LGPL-vs-GPL licensing issues.

One other thing: I'm implementing a slightly different version for 
Gnulib that uses ptrdiff_t rather than size_t for sizes (and is LGPL 
rather than GPL since it will clearly have uses in library situations). 
Using ptrdiff_t improves reliability, since one can compile with 
-fsanitize=undefined to catch integer overflow with size calculations. 
Over the years we have found that using size_t for byte and object 
counts leads to problems for which there is no effective automated 
checking. This is why I suggest that new memory-allocation APIs use 
ptrdiff_t rather than size_t.

  parent reply	other threads:[~2017-06-01 18:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-22 15:46 Florian Weimer
2017-04-24 14:06 ` Joseph Myers
2017-05-05 11:48   ` Florian Weimer
2017-05-05 15:13     ` Paul Eggert
2017-05-05 15:23       ` Florian Weimer
2017-05-05 22:31         ` Paul Eggert
2017-05-20  2:01 ` Carlos O'Donell
2017-05-21  0:43   ` Paul Eggert
2017-06-01 16:13     ` Carlos O'Donell
2017-06-01 17:09       ` Jeff Law
2017-06-01 20:21         ` Florian Weimer
2017-06-01 21:13           ` Adhemerval Zanella
2017-06-01 18:08       ` Paul Eggert [this message]
2017-05-30 12:48   ` Florian Weimer
2017-06-02  7:37     ` Carlos O'Donell
2017-06-02 10:04       ` Florian Weimer
2017-06-06 15:30       ` Stefan Liebler
2017-06-06 15:46         ` H.J. Lu
2017-06-07  9:54           ` Florian Weimer
2017-06-07  9:41         ` Florian Weimer
2017-06-07 14:41           ` Stefan Liebler
2017-06-07 18:56             ` Florian Weimer

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=91d54a00-2c61-52a8-76d6-3d035f1acfd5@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /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).