public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Kahle <tomka@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] ntl bump
Date: Sun, 29 Mar 2015 08:26:33 +0200	[thread overview]
Message-ID: <55179B19.7010501@gentoo.org> (raw)
In-Reply-To: <A6BAECEB-3B94-44E6-A272-58ECC73ABAA3@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

no problem. I'll bump it (but not today).

On 28/03/15 20:54, François Bissey wrote:
> And Victor just announce ntl 9.0 on sage-devel:
> 
> With much trepidation, I have introduced a (hopefully minor)
> backward incompatibility into NTL.  
> 
> The interface to the single-precision modular arithmetic 
> routines has been modified slightly.
> This interface change allows for more flexible and more
> efficient implementation of these routines,
> which play a crucial role at many levels in NTL.
> 
> Basically, these changes to the interface abstract away
> some implementation details that arguably should never been there
> in the first place.
> By coding to the new interface, NTL clients will be able to 
> benefit from the current and future improvements.
> 
> In particular, on 64-bit x86/GCC platforms, single precision
> moduli can now be up to 60 bits, rather than 50 bits.
> While some operations may in fact be a little slower, the most important
> ones (like MulModPrecon) should not be.
> Using larger moduli speeds up a number of things, like ZZ_pX
> arithmetic, as fewer primes need to be used in Chinese Remaindering steps.
> Other applications benefit from larger moduli as well.
> 
> It is expected that most NTL clients will not be affected at all.
> Moreover, any code that needs to be updated will be detected
> by the compiler, and the updates should be simple and mechanical.
> There is also a configuration flag that will enable the legacy
> interface (although this is not recommended practice).
> 
> For more, go to http://www.shoup.net/ntl
> 
> 

-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 536 bytes --]

  reply	other threads:[~2015-03-29  6:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 16:08 [gentoo-science] ntl bump Thomas Kahle
2015-03-25 21:48 ` François Bissey
2015-03-26 10:18   ` Thomas Kahle
2015-03-26 12:48     ` Thomas Kahle
2015-03-28 19:54       ` François Bissey
2015-03-29  6:26         ` Thomas Kahle [this message]
2015-04-02 12:33         ` Thomas Kahle
2015-04-02 22:53           ` François Bissey
2015-04-03  7:52             ` Thomas Kahle
2015-04-03  8:13               ` François Bissey
2015-04-03 10:12                 ` Thomas Kahle
2015-04-03 12:24                   ` François Bissey
2015-07-08 23:12                     ` François Bissey
2015-07-10  0:07                       ` François Bissey
2015-07-10  6:23                         ` Thomas Kahle
2015-07-10 10:05                           ` François Bissey
2015-07-10 10:52                             ` François Bissey
2015-07-10 14:16                               ` Thomas Kahle
2015-07-13  2:27                                 ` François Bissey

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=55179B19.7010501@gentoo.org \
    --to=tomka@gentoo.org \
    --cc=gentoo-science@lists.gentoo.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