From: Florian Weimer <fweimer@redhat.com>
To: Jeff Law <law@redhat.com>, Carlos O'Donell <carlos@redhat.com>,
Paul Eggert <eggert@cs.ucla.edu>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Dynamic growable arrays for internal use
Date: Thu, 01 Jun 2017 20:21:00 -0000 [thread overview]
Message-ID: <6c275b0c-1217-0044-a1ab-2af450028874@redhat.com> (raw)
In-Reply-To: <ec8b9318-4d95-ce6a-1511-7b63ebf16304@redhat.com>
On 06/01/2017 07:09 PM, Jeff Law wrote:
> FWIW, we use a 1.5 growth factor for similar situations within GCC.
Once we have a set of internal users, I plan to add an stap probe which
logs the final sizes (and the element type etc.), and then we can
revisit the growth policy. My hope is that very few dynarrays will ever
hit the heap, but we'll see.
Thanks,
Florian
next prev parent reply other threads:[~2017-06-01 20:21 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 [this message]
2017-06-01 21:13 ` Adhemerval Zanella
2017-06-01 18:08 ` Paul Eggert
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=6c275b0c-1217-0044-a1ab-2af450028874@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=law@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).