From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Cc: Philip Munts <phil@munts.net>
Subject: Re: How to disable per-local string functions?
Date: Mon, 20 Mar 2017 10:58:00 -0000 [thread overview]
Message-ID: <20170320105804.GI16777@calimero.vinschen.de> (raw)
In-Reply-To: <6ccd4b02-8a5e-feb6-cfb2-266bbd280e1d@munts.net>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
On Mar 19 08:24, Philip Munts wrote:
> I have a resource constrained Cortex-M0 application that fails with
> newlib 2.5.0. The strncasecmp() function is now pulling in a lot of
> locale handling code, which I presume results from commit
> c1b7d9d93dc8e88693162c0d984a114371919fdd, "Implement per-locale string
> functions".
>
> How can I either build newlib, or build my application to use the
> original string functions instead of the new *_l locale handling
> string functions?
strncasecmp does not use strncasecmp_l. It just calls tolower, which
calls isupper, which in turn calls a function accessing the
__global_locale struct. I *think* the problem is that this pulls in all
of libc/locale/locale.c, so the problem could perhaps alleviated by
moving __locale_ctype_ptr() and the __global_locale struct to separate
files...?
When I implemented this functionality I asked specificially for input
from users of small targets. I tried to keep the footprint as small as
possible, but there's very likely room for further improvement.
So, here's my request again: If somebody has problems with the size
of the code due to the locale stuff, please provide patches.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-03-20 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 7:25 Philip Munts
2017-03-20 10:58 ` Corinna Vinschen [this message]
2017-03-20 12:33 ` Philip Munts
2017-03-21 0:12 ` Hans-Bernhard Bröker
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=20170320105804.GI16777@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
--cc=phil@munts.net \
/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).