From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: Prakhar Bahuguna <prakhar.bahuguna@arm.com>, newlib@sourceware.org
Cc: nd@arm.com
Subject: Re: Memory usage of __global_locale for non-locale functions
Date: Fri, 26 May 2017 17:52:00 -0000 [thread overview]
Message-ID: <bf3a89d1-bc7e-7c75-729a-617b0dc401fb@t-online.de> (raw)
In-Reply-To: <20170526133112.mh6nbz2bvn6t2fp5@e107464-lin.cambridge.arm.com>
Am 26.05.2017 um 15:31 schrieb Prakhar Bahuguna:
> We've noticed that since a series of patches to add support for POSIX-1.2008
> per-thread locales in August 2015, the size of the .data section in binaries
> produced by our toolchain has increased significantly due to the
> __global_locale struct in lib_a-locale.o. This is linked in when any strto*()
> function is called. This is true even for non-locale functions such as
> strtoul().
Your classification of stroul() as a non-locale function is wrong.
This general issue has come up before, quite recently:
https://sourceware.org/ml/newlib/2017/msg00192.html
The answer for you is the same as it was then: a library that does
support setlocale at all has little chance but to pull in the required
machinery as soon as any of the localized standard library functions (or
macros) is referred to by the program.
And no, I don't think there's a configure-time option to disable locale
altogether.
next prev parent reply other threads:[~2017-05-26 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 13:31 Prakhar Bahuguna
2017-05-26 17:52 ` Hans-Bernhard Bröker [this message]
2017-05-30 8:17 ` Prakhar Bahuguna
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=bf3a89d1-bc7e-7c75-729a-617b0dc401fb@t-online.de \
--to=hbbroeker@t-online.de \
--cc=nd@arm.com \
--cc=newlib@sourceware.org \
--cc=prakhar.bahuguna@arm.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).