From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Joseph Myers <joseph@codesourcery.com>
Cc: maskray@google.com, libc-alpha@sourceware.org
Subject: Re: [PATCH] stdlib/longlong.h: Remove lvalue to rvalue conversion
Date: Tue, 12 Oct 2021 08:35:29 +0200 [thread overview]
Message-ID: <mwlf2yvjgu.fsf@tomate.loria.fr> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110112158040.1524986@digraph.polyomino.org.uk> (message from Joseph Myers on Mon, 11 Oct 2021 21:58:52 +0000)
Dear Joseph,
there was no change in the license from GMP 6.1.0 to the current version
(6.2.1). It is either under LGPL v3+ or GPL v2+ (at the user choice).
Thus if the version in the glibc is from GMP 6.1.0, we can update to the
current version.
Paul
> Date: Mon, 11 Oct 2021 21:58:52 +0000
> From: Joseph Myers <joseph@codesourcery.com>
> User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
> Cc: GNU C Library <libc-alpha@sourceware.org>
>
> On Sun, 10 Oct 2021, Fangrui Song via Libc-alpha wrote:
>
> > GCC longlong.h is almost the same as glibc longlong.h.
> > gmplib longlong.h is 500 lines longer and needs more work.
> > I don't know how to contribute to gmplib, hope a GCC dev (like you:))
> > can apply the patch there if acceptable.
>
> The GMP version diverged a very long time ago and now has a different
> license, so probably isn't suitable for merging code to GCC or glibc.
>
> --
> Joseph S. Myers
> joseph@codesourcery.com
>
next prev parent reply other threads:[~2021-10-12 6:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 22:14 Fangrui Song
2021-10-10 22:21 ` Andrew Pinski
2021-10-10 23:15 ` Fangrui Song
2021-10-11 8:55 ` Paul Zimmermann
2021-10-11 21:58 ` Joseph Myers
2021-10-12 6:35 ` Paul Zimmermann [this message]
2021-10-12 13:51 ` Joseph Myers
2021-10-12 6:31 ` Florian Weimer
2021-10-12 7:24 ` Fāng-ruì Sòng
2021-10-12 7:59 ` Florian Weimer
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=mwlf2yvjgu.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=maskray@google.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).