Why GMP doesn't support MinGW anymore?

[Andrey Khalyavin]

One thing I learnt since last e-mail - MinGW haven't been compiled as
64-bit binaries by anyone before. One may still need 64-bit gmp though.

2012/6/19 Torbjorn Granlund <tg at gmplib.org>

> Andrey Khalyavin <halyavin at google.com> writes:
>
>  I'm trying to compile MinGW what is impossible without GMP. I tried to use
>  newest version 5.0.5. But when I try to compile gcc, compiled compiler
>  immediately crashes. The source of the crash is __gmpn_cpuid function in
>  mpn\x86_64\fat\fat_entry.asm . This function uses Linux AMD64 calling
>  convention instead of Windows AMD64 one needed for MinGW. Can GMP use
>  conditional compilation to provide a suitable version of this function?
>
> I have no guess how you ended up with a build that includes assembly
> code unsuitable for your host.

There aren't any suitable assembly code for 64-bit Windows. So build can't
include it. That's why configure parameters doesn't matter.


> Perhaps this is a GMP bug, perhaps you
> worked around GMP's configure mechanims.
>
This is more like absence of MinGW 64 bit support than a bug.


> http://gmplib.org/manual/Reporting-Bugs.html
>
> --
> Torbjörn


2012/6/19 Torbjorn Granlund <tg at gmplib.org>

> Andrey Khalyavin <halyavin at google.com> writes:
>
>  I'm trying to compile MinGW what is impossible without GMP. I tried to use
>  newest version 5.0.5. But when I try to compile gcc, compiled compiler
>  immediately crashes. The source of the crash is __gmpn_cpuid function in
>  mpn\x86_64\fat\fat_entry.asm . This function uses Linux AMD64 calling
>  convention instead of Windows AMD64 one needed for MinGW. Can GMP use
>  conditional compilation to provide a suitable version of this function?
>
> I have no guess how you ended up with a build that includes assembly
> code unsuitable for your host.  Perhaps this is a GMP bug, perhaps you
> worked around GMP's configure mechanims.
>
> http://gmplib.org/manual/Reporting-Bugs.html
>
> --
> Torbjörn
>