[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Enlarge MAX_ALLOCA?
From: |
Eli Zaretskii |
Subject: |
Re: Enlarge MAX_ALLOCA? |
Date: |
Fri, 20 Jun 2014 21:36:15 +0300 |
> Date: Fri, 20 Jun 2014 19:44:46 +0400
> From: Dmitry Antipov <address@hidden>
> CC: "Herring, Davis" <address@hidden>, "address@hidden" <address@hidden>,
> "address@hidden" <address@hidden>
>
> 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?
Once again, this is not what the work area is used for, please read my
message where I mentioned the 2 functions which need this work area.
- 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, 2014/06/20
- Re: Enlarge MAX_ALLOCA?,
Eli Zaretskii <=
- 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