Sorry for the typos in the previous post, and I apologize if I
misrepresent anyone or anything.
>> If this is too specialized to go into gnulib, would it be easy for a
>> project to use its own replacement functions instead of the ones from
>> gnulib?
For this, can't the caller (info-utils.c) sim
Gavin Smith writes:
> On Sun, Feb 1, 2015 at 10:07 AM, Daiki Ueno wrote:
>> Eli Zaretskii writes:
>>
>>> Perhaps we could call _configthreadlocale to see if the value of
>>> setlocale can be cached?
>>
>> Yes, but then we would need to hook setlocale to invalidate the cache,
>> and currently th
On Sun, Feb 1, 2015 at 10:07 AM, Daiki Ueno wrote:
> Eli Zaretskii writes:
>
>> Perhaps we could call _configthreadlocale to see if the value of
>> setlocale can be cached?
>
> Yes, but then we would need to hook setlocale to invalidate the cache,
> and currently the setlocale module is not liste
> From: Daiki Ueno
> Cc: gavinsmith0...@gmail.com, bug-gnulib@gnu.org
> Date: Sun, 01 Feb 2015 19:07:35 +0900
>
> Perhaps it might be easier to add a new API to localcharset for
> single-threaded / single-locale consumer.
That might be the easiest short-term solution, yes.
Thanks.
Eli Zaretskii writes:
> Perhaps we could call _configthreadlocale to see if the value of
> setlocale can be cached?
Yes, but then we would need to hook setlocale to invalidate the cache,
and currently the setlocale module is not listed in the dependencies of
localcharset. I'm wondering if it is
> From: Daiki Ueno
> Cc: gavinsmith0...@gmail.com, bug-gnulib@gnu.org
> Date: Sun, 01 Feb 2015 03:52:20 +0900
>
> Eli Zaretskii writes:
>
> > Thanks. This improves things, but unfortunately not enough. The
> > reason is that call to setlocale at the beginning of locale_charset,
> > which is
Eli Zaretskii writes:
> Thanks. This improves things, but unfortunately not enough. The
> reason is that call to setlocale at the beginning of locale_charset,
> which is always made. If I replace that call with a constant string,
> I get a 20-fold speedup, and the display of large nodes in the
> From: Daiki Ueno
> Cc: Eli Zaretskii , bug-gnulib@gnu.org
> Date: Tue, 27 Jan 2015 15:14:36 +0900
>
> I took a bit more serious attempt to this, and ended up with the
> attached patch. Using the following test program:
>
> #include "config.h"
> #include "localcharset.h"
> #include
>
>
Very nice.
thanks,
Pádraig.
Daiki Ueno writes:
> Gavin Smith writes:
>
>> It appears you can have thread-local variables with gcc using
>> "__thread", for example, "static __thread const char *encoding". (I
>> don't know about other compilers.) Would something like this work? As
>> well as threads, updating the cached enco
Gavin Smith writes:
> It appears you can have thread-local variables with gcc using
> "__thread", for example, "static __thread const char *encoding". (I
> don't know about other compilers.) Would something like this work? As
> well as threads, updating the cached encoding when the encoding
> cha
11 matches
Mail list logo
