MPIR and gcc-4.3.2

[Jeroen Demeyer]

So what's the motivation for refusing to build MPIR with gcc-4.3.2?

The configure script essentially just says "it's broken" without
specifying how or why. I have built MPIR with gcc-4.3.2 on a GNU/Linux
x86_64 system with -march=nocona and built gcc with that MPIR and I had
no problems at all.

[Nils Bruin]

Both GMP and MPIR documentation complain about gcc-4.3.2, but I
haven't seen an explicit code snippet that triggers faulty behaviour.
Closest I found was this:

http://trac.mpir.org/mpir_trac/ticket/291

which indicates that at least something in "rootrem.c" goes wrong. I'd
assume the testsuites of both GMP and MPIR pick up on the problem, so
if you're finding everything is fine, it might be worth investigating.

[Bill Hart]

This thread got a lot of replies on mpir-devel which didn't show up
here for various random reasons.

The gist is that the problem only occurs with debian gcc 4.3.2, and
only with fstrict-aliasing which is enabled by -O2.

There's a discussion there about what best to do about it in Sage and
MPIR. I refer you to mpir-devel for the follow up.

Bill.