From: Dmitry Antipov <dmantipov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: "handa@gnu.org" <handa@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Enlarge MAX_ALLOCA?
Date: Fri, 20 Jun 2014 19:44:46 +0400 [thread overview]
Message-ID: <53A456EE.5050704@yandex.ru> (raw)
In-Reply-To: <B393F5AD12955C48A84FFB08032CD04F3B0D76F2@ECS-EXG-P-MB01.win.lanl.gov>
On 06/20/2014 07:15 PM, Herring, Davis wrote:
> We could also allocate it less frequently by allocating it statically
> (unless en/decoding can be reentrant, which seems unlikely).
We can also estimate its size before blindly allocating 64 (or 32, or
whatever else). For example, if we decode from 16-character string
to *code-conversion-work*, we need...hm, what's the upper bound?
May be 16 * MAX_MULTIBYTE_LENGTH?
Dmitry
next prev parent reply other threads:[~2014-06-20 15:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 16:02 Enlarge MAX_ALLOCA? Eli Zaretskii
2014-06-19 16:23 ` David Kastrup
2014-06-19 16:48 ` Eli Zaretskii
2014-06-19 17:04 ` David Kastrup
2014-06-19 17:14 ` Eli Zaretskii
2014-06-19 17:36 ` David Kastrup
2014-06-19 17:51 ` Eli Zaretskii
2014-06-19 18:21 ` Stefan Monnier
2014-06-19 21:13 ` David Kastrup
2014-06-20 7:10 ` Eli Zaretskii
2014-06-20 8:08 ` David Kastrup
2014-06-20 8:38 ` Dmitry Antipov
2014-06-20 8:56 ` Eli Zaretskii
2014-06-20 9:26 ` Andreas Schwab
2014-06-20 9:38 ` David Kastrup
2014-06-19 18:28 ` Stefan Monnier
2014-06-19 18:38 ` Eli Zaretskii
2014-06-19 20:37 ` Stefan Monnier
2014-06-20 7:08 ` Eli Zaretskii
2014-06-20 13:02 ` Stefan Monnier
2014-06-20 13:18 ` Eli Zaretskii
2014-06-20 14:43 ` Stefan Monnier
2014-06-20 14:50 ` Eli Zaretskii
2014-06-20 15:15 ` Herring, Davis
2014-06-20 15:44 ` Dmitry Antipov [this message]
2014-06-20 18:36 ` Eli Zaretskii
2014-06-21 13:01 ` K. Handa
2014-06-21 13:59 ` Eli Zaretskii
2014-06-21 17:08 ` Stefan Monnier
2014-06-22 9:22 ` K. Handa
2014-06-28 14:15 ` K. Handa
2014-06-28 14:38 ` Eli Zaretskii
2014-06-21 15:19 ` David Kastrup
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=53A456EE.5050704@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.