public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Nem W Schlecht <nemws1@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: gmp-6.1.0-1
Date: Tue, 17 Nov 2015 22:24:00 -0000	[thread overview]
Message-ID: <CA+2x6-+BskiDO-wDNrSOcAdn-4PtLO635-v2z0YcuDFCApxgMA@mail.gmail.com> (raw)
In-Reply-To: <announce.87a8qpctme.fsf@Rainer.invalid>

Hallo!

Today I noticed that some of my Perl DBI scripts (connecting to MSSQL)
had been failing since Nov 10th (causing perl core dumps).  Thinking
it was just a needed re-compile, I recompiled DBD::Sybase, which
compiled fine, but core dumped during testing.  I then tried to
recompile the DBI module and that was causing gcc to core dump!

I went through my list of installs from that day and eventually found
that this update was causing the problem.  I backed it from 6.1.0-1 to
6.0.0a-2 and now everything is working just fine again for me
(DBD::Sybase and compiling DBI).

Nothing else seems to be affected by this - just my database access (I
don't use another database on this host).  I have another host running
cygwin that is very close to this host (Windows 7 x64, Cygwin 2.3.1)
and it does *NOT* have the same issue.  Both are running SQL Server
2014 Developer (x64).

I'd be happy to help debug this issue, but I'm not sure where to
start.  Any suggestions?


On Sat, Nov 7, 2015 at 4:49 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> GNU Multiple Precision Arithmetic Library
> =========================================
>
> GMP is a free library for arbitrary precision arithmetic, operating on
> signed integers, rational numbers, and floating point numbers. There is
> no practical limit to the precision except the ones implied by the
> available memory in the machine GMP runs on. GMP has a rich set of
> functions, and the functions have a regular interface.
>
> Version 6.1.0 is an upstream release fully binary and ABI compatible
> with the 6.0.0 and 5.x versions.
>
> --8<---------------cut here---------------start------------->8---
> GMP 6.1.0 release announcement
>
> BUGS FIXED
>
>     The public function mpn_com is now correctly declared in gmp.h.
>
>     Healed possible failures of mpn_sec_sqr for non-cryptographic sizes
>     for some obsolete CPUs.
>
>     The option --disable-assembly now disables all inlined asm.
>
>     Fixed bug affecting mini-gmp's bitwise functions mpz_setbit,
>     mpz_clrbit, and mpz_combit.
>
>     Various problems related to precision for mpf have been fixed.
>
>     Fixed ABI incompatible stack alignment in calls from assembly code.
>
>     Fixed PIC bug in popcount affecting Intel processors using the
>     32-bit ABI.
>
>
> SPEEDUPS
>
>     Speedup for Intel Broadwell and Skylake though assembly code making
>     use of new ADX instructions.
>
>     Square root is now faster when the remainder is not needed. Also the
>     speed to compute the k-th root improved, for small sizes.
>
>     Improved arm64 support.
>
>
> FEATURES
>
>     New C++ functions gcd and lcm for mpz_class.
>
>     New public mpn functions mpn_divexact_1, mpn_zero_p, and
>     mpn_cnd_swap.
>
>     New public mpq_cmp_z function, to efficiently compare rationals with
>     integers.
>
>     Support for Darwin in all x86 code, thereby enabling fat builds on
>     Darwin.
>
>     Support for more 32-bit arm processors.
>
>     Support for compilation with clang/llvm on more platforms. Caution:
>     GMP triggers mis-compilation bugs in clang for many platforms, such
>     as arm, x86 (32-bit and 64-bit), powerpc, mips.
>
>     Support for AVX-less modern x86 CPUs. (Such support might be missing
>     either because the CPU vendor chose to disable AVX, or because the
>     running kernel lacks AVX context switch support.)
>
>     Stack usage trimmed; we believe 512 KiB is now sufficient for any
>     GMP call, irrespective of operand size.
>
>     Support for NetBSD under Xen; we switch off AVX unconditionally
>     under NetBSD since a bug in NetBSD makes AVX fail under Xen.
>
>
> MISC
>
>     We now use manufacturers' code names for x86 CPUs, e.g., "haswell"
>     instead of names derived from the commercial brands.
>
>     Small improvements and better coverage for the test suite.
>
>     The various FreeBSD problems listed for 6.0.0 affect this release
>     too.
>
>     Tuned values for FFT multiplications are provided for larger number
>     on many platforms.
>
>
>
> This release would not have been possible without the continuous work of
> improvement, revision and refinement by the whole GMP team: Torbjörn
> Granlund, Niels Möller, Marco Bodrato, and Marc Glisse.
>
> Please see the GMP manual for a complete list of GMP contributors.
>


-- 
Nem W Schlecht
 "Perl did the magic.  I just waved the wand."

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2015-11-17 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08  0:55 Achim Gratz
2015-11-17 22:24 ` Nem W Schlecht [this message]
2015-11-19  7:48   ` gmp-6.1.0-1 Achim Gratz
2015-11-19  8:13     ` gmp-6.1.0-1 Achim Gratz
2015-11-19  7:49   ` gmp-6.1.0-1 Achim Gratz

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=CA+2x6-+BskiDO-wDNrSOcAdn-4PtLO635-v2z0YcuDFCApxgMA@mail.gmail.com \
    --to=nemws1@gmail.com \
    --cc=cygwin@cygwin.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).