unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: What version of GMP should we require?
Date: Thu, 24 Feb 2011 20:39:54 +0100	[thread overview]
Message-ID: <871v2xw7at.fsf@gnu.org> (raw)
In-Reply-To: 87y657wn54.fsf@netris.org

Hi Mark,

Mark H Weaver <mhw@netris.org> writes:

> I recently noticed that scm_i_big2dbl contains some crufty and
> inefficient compatibility code to work around unspecified rounding
> behavior of mpz_get_d in GMP prior to version 4.2.  GMP 4.2 was released
> in March 2006 and has been in Debian since sarge (now oldstable).
>
> How would you feel about making Guile 2.0.x require GMP 4.2 or later?

I like the suggestion, but I’m uncomfortable with making this change in 2.0.

> I was hoping to apply these changes to the 2.0 branch, but
> exact-integer-root and the enhancements to expt depend on mpz_rootrem,
> which was introduced in GMP 4.2.  I could reimplement its functionality
> if needed, but the result would surely be somewhat slower.

For 2.0, what about AC_CHECK_LIB ‘mpz_rootrem’, and provide a
replacement when it’s not available?  It doesn’t really matter if the
replacement is slower since less and less people will need it, but
still, that would allow us to not break people’s expectations regarding
compatibility.

In ‘master’ you can of course require 4.2 and clean things up as you see
fit.  :-)

How would that work for you?

Thanks,
Ludo’.




  parent reply	other threads:[~2011-02-24 19:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23  1:33 What version of GMP should we require? Mark H Weaver
2011-02-23 15:40 ` Mark H Weaver
2011-02-24 19:39 ` Ludovic Courtès [this message]
2011-02-24 20:20   ` Mark H Weaver

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871v2xw7at.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.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).