From: Eric Blake <eblake@redhat.com>
To: cygwin-developers@cygwin.com
Subject: Re: [newlib-cygwin] Redefine locale info in struct _reent for per-thread locales
Date: Wed, 06 Jul 2016 15:23:00 -0000 [thread overview]
Message-ID: <577D224E.9070304@redhat.com> (raw)
In-Reply-To: <20160706134145.119102.qmail@sourceware.org>
[-- Attachment #1.1: Type: text/plain, Size: 1372 bytes --]
On 07/06/2016 07:41 AM, Corinna Vinschen wrote:
> https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=a68ca43b9014ae45feb3162a5f066524e2b38e1a
>
> commit a68ca43b9014ae45feb3162a5f066524e2b38e1a
> Author: Corinna Vinschen <corinna@vinschen.de>
> Date: Wed Jul 6 15:41:35 2016 +0200
>
> Redefine locale info in struct _reent for per-thread locales
> +++ b/newlib/libc/include/sys/reent.h
> @@ -37,6 +37,11 @@ typedef __uint32_t __ULong;
>
> struct _reent;
>
> +/* TODO: This structure type isn't defined yet. It's supposed to be used
> + by locale-specific functions in case a pre-thread locale per SUSv4 has
s/pre/per/
> + been specified. */
> +struct _thr_locale_t;
> +
> /*
> * If _REENT_SMALL is defined, we make struct _reent as small as possible,
> * by having nearly everything possible allocated at first use.
> @@ -384,8 +389,9 @@ struct _reent
>
> int __sdidinit; /* 1 means stdio has been init'd */
>
> - int _current_category; /* unused */
> - _CONST char *_current_locale; /* unused */
> + /* TODO */
> + int _unspecified_locale_info; /* unused, reserved for locale stuff */
> + struct _thr_locale_t *_locale;/* per-thread locale */
Looks like a good useful start.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next parent reply other threads:[~2016-07-06 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160706134145.119102.qmail@sourceware.org>
2016-07-06 15:23 ` Eric Blake [this message]
2016-07-06 16:24 ` Corinna Vinschen
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=577D224E.9070304@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin-developers@cygwin.com \
/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).