From: Joel Sherrill <joel@rtems.org>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: Keith Packard <keithp@keithp.com>, Newlib <newlib@sourceware.org>,
christoph.lauter@christoph-lauter.org,
Jean-Michel.Muller@ens-lyon.fr, sibid@uvic.ca
Subject: Re: correctly rounded mathematical functions
Date: Wed, 5 Jan 2022 13:00:35 -0600 [thread overview]
Message-ID: <CAF9ehCWJMRSdHQqo6joqyjYr6NAYZMOVS5eYgCEfrm6Rz680Qg@mail.gmail.com> (raw)
In-Reply-To: <mwmtkao1gz.fsf@tomate.loria.fr>
I hate to ask since I know this is unrelated but what is the best source for
properly licensed and accurate long double methods. I am still hoping that
part of an RTEMS GSoC project is to merge them from somewhere into
newlib.
And I'm thrilled at all the autoconf/automake work. That has really
been a challenge
for students.
On Wed, Jan 5, 2022 at 5:39 AM Paul Zimmermann <Paul.Zimmermann@inria.fr> wrote:
>
> Hi Keith,
>
> > Yeah, I've forked newlib into 'picolibc' and have removed all of the
> > non-BSD licensed files to make the license status of that project
> > clearly BSD only. All of the non-BSD files are used to build the library
> > only for specific targets; the general library code is all BSD licensed.
> >
> > Something BSD-ish would preserve the license status of newlib built for
> > embedded targets, and would also be usable by picolibc.
>
> then I guess the MIT license would be ok for both newlib and picolibc,
> since it is more permissive than the BSD license.
>
> Best regards,
> Paul
next prev parent reply other threads:[~2022-01-05 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 12:57 Paul Zimmermann
2022-01-03 20:41 ` Joel Sherrill
2022-01-04 9:44 ` Paul Zimmermann
2022-01-04 15:23 ` Joel Sherrill
2022-01-04 15:44 ` Paul Zimmermann
2022-01-04 18:01 ` Jeff Johnston
2022-01-05 10:33 ` Paul Zimmermann
2022-01-04 18:50 ` Keith Packard
2022-01-05 11:39 ` Paul Zimmermann
2022-01-05 19:00 ` Joel Sherrill [this message]
2022-01-06 10:12 ` Paul Zimmermann
2022-01-06 14:51 ` Joel Sherrill
2022-01-06 15:33 ` Paul Zimmermann
2022-01-05 19:43 ` Keith Packard
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=CAF9ehCWJMRSdHQqo6joqyjYr6NAYZMOVS5eYgCEfrm6Rz680Qg@mail.gmail.com \
--to=joel@rtems.org \
--cc=Jean-Michel.Muller@ens-lyon.fr \
--cc=Paul.Zimmermann@inria.fr \
--cc=christoph.lauter@christoph-lauter.org \
--cc=keithp@keithp.com \
--cc=newlib@sourceware.org \
--cc=sibid@uvic.ca \
/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).