Marc Glisse writes:
> Niels, is enough of this text yours that we don't need an assignment
> from Emmanuel?
I think so. My text originally posted here:
https://gmplib.org/list-archives/gmp-devel/2018-May/005000.html
> Do you want to commit it yourself, or would you rather
> I do it?
Please go
On Fri, 11 Jun 2021, Emmanuel Thomé wrote:
On Thu, Jun 10, 2021 at 03:02:25PM +0200, Marc Glisse wrote:
On Thu, 10 Jun 2021, Emmanuel Thomé wrote:
> And as it turns out, we even discussed that very documentation bit about
> three years ago (here a link to an actual patch -- original discussion
On Thu, Jun 10, 2021 at 03:02:25PM +0200, Marc Glisse wrote:
> On Thu, 10 Jun 2021, Emmanuel Thomé wrote:
>
> > And as it turns out, we even discussed that very documentation bit about
> > three years ago (here a link to an actual patch -- original discussion
> > was in may 2018).
> >
> > https:/
On Thu, 10 Jun 2021, Emmanuel Thomé wrote:
And as it turns out, we even discussed that very documentation bit about
three years ago (here a link to an actual patch -- original discussion
was in may 2018).
https://gmplib.org/list-archives/gmp-devel/2019-January/005182.html
The description of m
And as it turns out, we even discussed that very documentation bit about
three years ago (here a link to an actual patch -- original discussion
was in may 2018).
https://gmplib.org/list-archives/gmp-devel/2019-January/005182.html
E.
On Thu, Jun 10, 2021 at 01:39:30PM +0200, Vincent Lefevre wrote
On 2021-06-09 20:29:35 +0200, Marc Glisse wrote:
> On Wed, 9 Jun 2021, Marco Bodrato wrote:
> > By the way, I think that also the documentation should be updated
> > accordingly.
>
> We have never documented mpz_ptr/mpz_srcptr, my patch does not change this
> discrepancy. Maybe this is a new motiv
On Wed, 9 Jun 2021, Marco Bodrato wrote:
Il 2021-05-12 15:17 Marc Glisse ha scritto:
the latest version of gcc has a new (questionable) warning that
complains if a function is declared as taking a mpz_t parameter and
redeclared as taking mpz_ptr, or the reverse.
We might as well be consistent a
Ciao,
Il 2021-05-12 15:17 Marc Glisse ha scritto:
the latest version of gcc has a new (questionable) warning that
complains if a function is declared as taking a mpz_t parameter and
redeclared as taking mpz_ptr, or the reverse.
We might as well be consistent and use pointers everywhere, as in t
Hello,
the latest version of gcc has a new (questionable) warning that complains
if a function is declared as taking a mpz_t parameter and redeclared as
taking mpz_ptr, or the reverse.
We might as well be consistent and use pointers everywhere, as in the
attached patch. Does someone disagree