[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Enlarge MAX_ALLOCA?
From: |
Dmitry Antipov |
Subject: |
Re: Enlarge MAX_ALLOCA? |
Date: |
Fri, 20 Jun 2014 19:44:46 +0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
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
- Re: Enlarge MAX_ALLOCA?, (continued)
- Re: Enlarge MAX_ALLOCA?, Stefan Monnier, 2014/06/19
- Re: Enlarge MAX_ALLOCA?, Eli Zaretskii, 2014/06/19
- Re: Enlarge MAX_ALLOCA?, Stefan Monnier, 2014/06/19
- Re: Enlarge MAX_ALLOCA?, Eli Zaretskii, 2014/06/20
- Re: Enlarge MAX_ALLOCA?, Stefan Monnier, 2014/06/20
- Re: Enlarge MAX_ALLOCA?, Eli Zaretskii, 2014/06/20
- Re: Enlarge MAX_ALLOCA?, Stefan Monnier, 2014/06/20
- Re: Enlarge MAX_ALLOCA?, Eli Zaretskii, 2014/06/20
- RE: Enlarge MAX_ALLOCA?, Herring, Davis, 2014/06/20
- Re: Enlarge MAX_ALLOCA?,
Dmitry Antipov <=
- Re: Enlarge MAX_ALLOCA?, Eli Zaretskii, 2014/06/20
- Re: Enlarge MAX_ALLOCA?, K. Handa, 2014/06/21
- Re: Enlarge MAX_ALLOCA?, Eli Zaretskii, 2014/06/21
- Re: Enlarge MAX_ALLOCA?, Stefan Monnier, 2014/06/21
- Re: Enlarge MAX_ALLOCA?, K. Handa, 2014/06/22
- Re: Enlarge MAX_ALLOCA?, K. Handa, 2014/06/28
- Re: Enlarge MAX_ALLOCA?, Eli Zaretskii, 2014/06/28
- Re: Enlarge MAX_ALLOCA?, David Kastrup, 2014/06/21