Oh, very interesting. I was not aware of that! Thank you.
Bill. On 9 May 2012 15:12, leif <not.rea...@online.de> wrote: > Bill Hart wrote: >> >> Sorry, I meant it was the rootrem code that fails. >> >> http://trac.mpir.org/mpir_trac/ticket/291 (I believe the information >> about it being a misexpansion of MPN_ZERO is incorrect -- it was much >> more fundamental, affecting simple for loops) >> >> >> http://us.generation-nt.com/answer/bug-524472-gcc-4-3-gcc-4-3-2-miscompiles-gmp-4-3-0-help-168491181.html > > > Ad-free: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524472 > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36765 > > Note that apparently *FSF* GCC 4.3.2 isn't affected, it's just Debian's. > > > -leif > > > >> On 9 May 2012 11:18, Bill Hart<goodwillh...@googlemail.com> wrote: >>> >>> The test that often fails is the (extended) gcd one. However, it is >>> unsafe to run MPIR with this gcc unpatched, even if the test code >>> passes, as wrong answers may be returned. It's a long time ago, but as >>> I recall, certain for loops in MPIR compiled incorrectly. This wasn't >>> a preparser problem, so all attempts to replace the code with >>> something alternative that worked, failed. Of course it would also >>> have meant analysing and rewriting whole swathes of MPIR even if we >>> did find a way to work around it. >>> >>> We didn't add a test for this to MPIR's test suite. But I have no idea >>> why the existing test suite doesn't fail for you. It certainly did on >>> the x86_64 machines I tried. >>> >>> As noted, the problem also affects GMP. >>> >>> Bill. >>> >>> On 9 May 2012 09:14, Jeroen Demeyer<jdeme...@cage.ugent.be> wrote: >>>> >>>> On 2012-05-09 10:05, Jason Moxham wrote: >>>>> >>>>> >>>>> 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. >>>>> >>>>> >>>>> ------------------------------------------------- >>>>> >>>>> gcc-4.3.2 fails MPIR's make check on x64 , I think it's the reuse test >>>>> , I suppose we should write a proper test so patched gcc's will work , but >>>>> I'm not at all sure what part of gcc is broken as we can't use the reuse >>>>> test itself as it needs MPIR to be built first. Note GMP is also broken on >>>>> gcc-4.3.2 >>>> >>>> >>>> Sorry, I should have mentioned that I did run the testsuite with >>>> gcc-4.3.2 and all tests passed. So if there really is a problem with >>>> gcc-4.3.2, the testsuite of MPIR-2.4.0 doesn't catch it. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "mpir-devel" group. >>>> To post to this group, send email to mpir-devel@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> mpir-devel+unsubscr...@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/mpir-devel?hl=en. >>>> >> > > > -- > () The ASCII Ribbon Campaign > /\ Help Cure HTML E-Mail > > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to mpir-devel@googlegroups.com. > To unsubscribe from this group, send email to > mpir-devel+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
