From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: Should libc/locale/lnumeric.c be in GENERAL_SOURCES (EL/IX level 1)?
Date: Mon, 23 Aug 2021 10:03:38 +0200 [thread overview]
Message-ID: <YSNWWuGlbxNzeM5R@calimero.vinschen.de> (raw)
In-Reply-To: <CAF9ehCXJsN07aKmd7CJUEyoycBDt1oLucZX21Jq+a5cO-tTTTg@mail.gmail.com>
On Aug 20 08:29, Joel Sherrill wrote:
> On Fri, Aug 20, 2021 at 3:32 AM Corinna Vinschen <vinschen@redhat.com> wrote:
> >
> > On Aug 19 17:26, Roger Sayle wrote:
> > >
> > >
> > > I believe that newlib/libc/locale/Makefile.am should place lnumeric.c
> > >
> > > in GENERAL_SOURCES [EL/IX level 1]. The motivation for doing this is
> > >
> > > that both stdlib/strtod.c and stdlib/gdtoa-gethex.c unconditionally
> > >
> > > call __get_numeric_locale, and they themselves are in GENERAL_SOURCES
> > >
> > > (i.e. EL/IX level 1).
>
> The FACE Technical Standard (https://opengroup.org/face) has four POSIX profiles
> which were designed with security and avionics certification in mind has no
> locale support in the lowest three profiles and only limited support
> in the largest
> profile.
>
> The Software Communications Architecture (SCA) has a few profiles and targets
> software defined radios
> (https://sds.wirelessinnovation.org/history-of-the-sca). It
> does not include any locale support. The intended users would likely also be
> subject to security audits.
>
> With that background, making locale as optional as possible is a good idea for
> footprint both in code size and what might need to be audited. I'm happy with
> the patch.
Pushed.
Thanks,
Corinna
prev parent reply other threads:[~2021-08-23 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 16:26 Roger Sayle
2021-08-20 8:32 ` Corinna Vinschen
2021-08-20 13:29 ` Joel Sherrill
2021-08-23 8:03 ` Corinna Vinschen [this message]
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=YSNWWuGlbxNzeM5R@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
/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).