parallel make bug in tune/ directory

2018-02-15 Thread Win C
This is a bug of the current mercurial repo in the tune/ directory: When I run `make -j6 allprogs` for the first time, an error was emitted: libtool: link: (cd .libs/libspeed.lax/libtests.a && ar x "/data/data/com.termux/files/home/gmp-unstable/tune/../tests/.libs/libtests.a") libtool: error

Re: parallel make bug in tune/ directory

2018-02-15 Thread Torbjörn Granlund
Win C writes: This is a bug of the current mercurial repo in the tune/ directory: When I run `make -j6 allprogs` for the first time, an error was emitted: libtool: link: (cd .libs/libspeed.lax/libtests.a && ar x "/data/data/com.termux/files/home/gmp-unstable/tune/../tests/.libs/li

Re: parallel make bug in tune/ directory

2018-02-15 Thread Vincent Lefevre
On 2018-02-15 12:50:46 +0100, Torbjorn Granlund wrote: > Win C writes: > > This is a bug of the current mercurial repo in the tune/ directory: > > When I run `make -j6 allprogs` for the first time, an error was emitted: > > > libtool: link: (cd .libs/libspeed.lax/libtests.a && ar x

Re: parallel make bug in tune/ directory

2018-02-15 Thread Torbjörn Granlund
Vincent Lefevre writes: The user always has the right to use the -j option if he wants to. Thanks for clarifying that, Vincent! Unfortunately, the result will be a build error in the tune subdir. But I assume the GMP developers have The Right to release GMP without parallel developer subdir

Re: parallel make bug in tune/ directory

2018-02-15 Thread Vincent Lefevre
On 2018-02-15 13:07:32 +0100, Torbjorn Granlund wrote: > Vincent Lefevre writes: > > The user always has the right to use the -j option if he wants to. > > Thanks for clarifying that, Vincent! > > Unfortunately, the result will be a build error in the tune subdir. But > I assume the GMP deve

Use of malloc in mpn_lshift_com optimization 2

2018-02-15 Thread Dennis Schridde
Hi! I noticed an issue in GMP 6.1.2 when compiling it with CFLAGS="-pipe -O2 - march=znver1" for x86-32 on Gentoo Linux (in chroot). Configure fails the "mpn_lshift_com optimization 2" test, because that test uses `malloc` where it should have used `calloc`, according to an investigation by Fre