Go Back > Factoring Projects > GMP-ECM

Thread Tools
Old 2011-06-22, 21:44   #1
ATH's Avatar
Dec 2003

37·83 Posts
Default Problem compiling latest SVN

WraithX helped me alot with various problems, now I'm down to an assembler compiling problem.

I can compile the official version 6.3 (ecm-6.3.tar.gz) without problem. Now I try the latest SVN and "autoreconf -i" and configure works but it failes in the beginning of "make" when I have --enable-asm-redc and --build=x86_64-w64-mingw32 or --build=x86_64-pc-mingw32 but works if --build=i686-pc-mingw32. With --disable-asm-redc it works with all the different --build.
Here is the error message:
$ make
make  all-recursive
make[1]: Entering directory `/home/ATH/ecm63svn1582mpir_1'
Making all in x86_64
make[2]: Entering directory `/home/ATH/ecm63svn1582mpir_1/x86_64'
m4 -I../ -DOPERATION_mulredc1 `test -f mulredc1.asm || echo './'`mulredc1.asm >m
/bin/sh ../libtool   --mode=compile gcc  -O2 -pedantic -m64 -std=gnu99 -mtune=co
re2 -march=core2 -c -o mulredc1.lo mulredc1.s
libtool: compile:  gcc -O2 -pedantic -m64 -std=gnu99 -mtune=core2 -march=core2 -
c mulredc1.s -o mulredc1.o
2/bin/as.exe: BFD (GNU Binutils) assertion fail ../../binutils-
mulredc1.s: Assembler messages:
mulredc1.s:59: Error: cannot represent relocation type BFD_RELOC_386_GOTPC
make[2]: *** [mulredc1.lo] Error 1
rm mulredc1.s
make[2]: Leaving directory `/home/ATH/ecm63svn1582mpir_1/x86_64'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ATH/ecm63svn1582mpir_1'
make: *** [all] Error 2
I also tried another version of mingw64 with a newer libtool/binutils.

If I find no answer to this, I'll have to use another --build with --enable-asm-redc. Which is best build for a quad core Q9450 when x86_64 doesn't work. i686 or i786? or some other? there is also i886 and i986 but the assembler code not supported, but I'm curious which processors those cover. With --build=i686-pc-mingw32 it says "Using asm redc code from directory athlon" and with --build=i786-pc-mingw32 it says "Using asm redc code from directory pentium4" so I guess non of those are great.

I use the CFLAGS -mtune=core2 -march=core2 so how important is --build?

Last fiddled with by ATH on 2011-06-22 at 21:50
ATH is offline   Reply With Quote
Old 2011-06-23, 01:06   #2
WraithX's Avatar
Mar 2006

11×43 Posts

Now that I've looked at the "offending" line in mulredc.s, I see that:
`	jz	1f
	lea     _GLOBAL_OFFSET_TABLE_(%rip), %rbx
So, if I remember right, just pass in --disable-assert to the configure script, and this problem should go away. In the official gmp-ecm 6.3 release, assert is not turned on, and this is why that was building successfully for you. Let us know how it goes.
WraithX is offline   Reply With Quote
Old 2011-06-23, 07:27   #3
ATH's Avatar
Dec 2003

37·83 Posts

You are correct again of course It works, thanks alot for all your help.

I thought assertion was enabled by default in the official release, but I forgot that was back during release candidates:

I guess it's ok to run without assertions? I'll test it a bit anyway.

Last fiddled with by ATH on 2011-06-23 at 07:28
ATH is offline   Reply With Quote

Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
Intel's latest problem... science_man_88 Hardware 19 2018-01-25 01:06
Problem compiling GMP-ECM with gwnum... WraithX GMP-ECM 9 2011-08-21 22:45
Problem compiling msieve with gcc 4.4.2 chris2be8 Msieve 5 2010-02-22 18:35
Bigint problem with snfs latest snapshot VJS Factoring 0 2006-07-10 22:25
Latest version? [CZ]Pegas Software 3 2002-08-23 17:05

All times are UTC. The time now is 00:59.

Tue Apr 13 00:59:09 UTC 2021 up 4 days, 19:40, 1 user, load averages: 1.96, 2.06, 2.26

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.