version 2.6.0

Am Donnerstag, 26. Juni 2014 10:48:32 UTC+2 schrieb Bill Hart:
> Which version of MPIR? Does it happen with the MPIR-2.7.0-alpha?
> 
> 
> Bill.
> 
> 
> 
> On 26 June 2014 10:40, Jakob Kroeker <kro...@uni-math.gwdg.de> wrote:
> 
> Hello Bill,
> 
> 
> 
> 
> 
> i'm hitting a similar problem;
> 
> on my machine (Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz) several tests (e.g. 
> t-gcdext) fail in
> 
> 
> 
>   mulmod_2expp1_basecase.c:51: GNU MP assertion failed: !((xp) + (n) > (yp) 
> && (yp) + (n) > (xp))
> 
> 
> 
> when I enable the --enable-assert flag. Everything else is clean.
> 
> 
> 
> The OS is SL 6.5; gcc version 4.7.3
> 
> 
> 
> 
> 
> Jack
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Am Freitag, 28. März 2014 16:26:28 UTC+1 schrieb Bill Hart:
> 
> 
> > Hi Anton,
> 
> >
> 
> >
> 
> > I am unable to replicate this bug in our current master branch. I wonder if 
> > you could try checking it out and trying it again to see if the problem 
> > still occurs for you. If so, we can try to figure out why.
> 
> >
> 
> >
> 
> >
> 
> > git clone https://github.com/wbhart/mpir
> 
> >
> 
> > cd mpir
> 
> > ./configure --enable-cxx --enable-alloca --enable-gmpcompat --enable-assert
> 
> >
> 
> > make
> 
> > make check
> 
> >
> 
> >
> 
> > Bill.
> 
> >
> 
> >
> 
> >
> 
> 
> > On 4 January 2014 17:44, Bill Hart <goodwi...@googlemail.com> wrote:
> 
> >
> 
> >
> 
> > Hi,
> 
> >
> 
> >
> 
> > This looks like we have a bug in our alloca support. I'm afraid I haven't 
> > seen this bug before, so I don't know what to suggest, other thn to 
> > configure without alloca until we can fix the problem.
> 
> >
> 
> >
> 
> >
> 
> >
> 
> > I'll add this to our list of things that need fixing.
> 
> >
> 
> >
> 
> > Thanks for the report.
> 
> >
> 
> >
> 
> > Bill.
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> 
> 
> 
> > On 4 January 2014 16:49, Anton Mosunov <mosu...@gmail.com> wrote:
> 
> >
> 
> >
> 
> > Good day,
> 
> >
> 
> >
> 
> >
> 
> > I am having a difficulty installing mpir 2.6.0 on my system. I configure it 
> > with
> 
> >
> 
> >
> 
> >
> 
> > ./configure --prefix=/home/grads/asmosuno/local/ ABI=64 --enable-cxx 
> > --enable-gmpcompat --enable-alloca=alloca --enable-assert
> 
> >
> 
> >
> 
> >
> 
> > and after "make", during "make check" the following tests fail:
> 
> >
> 
> >
> 
> >
> 
> > ...
> 
> >
> 
> > PASS: t-fat
> 
> >
> 
> > /bin/sh: line 1:  3537 Aborted                 "$tst" > t-gcdext.log-t 2>&1
> 
> >
> 
> > FAIL: t-gcdext
> 
> >
> 
> > PASS: t-get_d
> 
> >
> 
> > PASS: t-hgcd
> 
> >
> 
> > PASS: t-instrument
> 
> >
> 
> > /bin/sh: line 1:  3662 Aborted                 "$tst" > t-inv_div_q.log-t 
> > 2>&1
> 
> >
> 
> > FAIL: t-inv_div_q
> 
> >
> 
> > /bin/sh: line 1:  3693 Aborted                 "$tst" > t-inv_div_qr.log-t 
> > 2>&1
> 
> >
> 
> > FAIL: t-inv_div_qr
> 
> >
> 
> > /bin/sh: line 1:  3724 Aborted                 "$tst" > 
> > t-inv_div_qr_n.log-t 2>&1
> 
> >
> 
> > FAIL: t-inv_div_qr_n
> 
> >
> 
> > /bin/sh: line 1:  3758 Aborted                 "$tst" > 
> > t-inv_divappr_q.log-t 2>&1
> 
> >
> 
> > FAIL: t-inv_divappr_q
> 
> >
> 
> > /bin/sh: line 1:  3792 Aborted                 "$tst" > 
> > t-inv_divappr_q_n.log-t 2>&1
> 
> >
> 
> > FAIL: t-inv_divappr_q_n
> 
> >
> 
> > /bin/sh: line 1:  3825 Aborted                 "$tst" > t-invert.log-t 2>&1
> 
> >
> 
> > FAIL: t-invert
> 
> >
> 
> > PASS: t-iord_u
> 
> >
> 
> > ...
> 
> >
> 
> >
> 
> >
> 
> > When I remove "--enable-alloca=alloca" flag, all the tests get passed 
> > successfully. The same problem persists when I use "malloc-reentrant" 
> > instead of "alloca".
> 
> >
> 
> >
> 
> >
> 
> > Here's an information on the one of the processors (other 63 are the same):
> 
> >
> 
> >
> 
> >
> 
> > -bash-4.1$ cat /proc/cpuinfo
> 
> >
> 
> > processor       : 0
> 
> >
> 
> > vendor_id       : GenuineIntel
> 
> >
> 
> > cpu family      : 6
> 
> >
> 
> > model           : 46
> 
> >
> 
> > model name      : Intel(R) Xeon(R) CPU           X7560  @ 2.27GHz
> 
> >
> 
> > stepping        : 6
> 
> >
> 
> > cpu MHz         : 2261.137
> 
> >
> 
> > cache size      : 24576 KB
> 
> >
> 
> > physical id     : 0
> 
> >
> 
> > siblings        : 16
> 
> >
> 
> > core id         : 0
> 
> >
> 
> > cpu cores       : 8
> 
> >
> 
> > apicid          : 0
> 
> >
> 
> > initial apicid  : 0
> 
> >
> 
> > fpu             : yes
> 
> >
> 
> > fpu_exception   : yes
> 
> >
> 
> > cpuid level     : 11
> 
> >
> 
> > wp              : yes
> 
> >
> 
> > flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov 
> > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp 
> > lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc 
> > aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca 
> > sse4_1 sse4_2 x2apic popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority 
> > ept vpid
> 
> 
> >
> 
> >
> 
> >
> 
> > bogomips        : 4522.27
> 
> >
> 
> > clflush size    : 64
> 
> >
> 
> > cache_alignment : 64
> 
> >
> 
> > address sizes   : 44 bits physical, 48 bits virtual
> 
> >
> 
> > power management:
> 
> >
> 
> >
> 
> >
> 
> > I would greatly appreciate your help.
> 
> >
> 
> >
> 
> >
> 
> > Sincerely,
> 
> >
> 
> > Anton
> 
> >
> 
> >
> 
> >
> 
> > --
> 
> >
> 
> > You received this message because you are subscribed to the Google Groups 
> > "mpir-devel" group.
> 
> >
> 
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to mpir-devel+...@googlegroups.com.
> 
> >
> 
> > To post to this group, send email to mpir-...@googlegroups.com.
> 
> 
> 
> >
> 
> > Visit this group at http://groups.google.com/group/mpir-devel.
> 
> >
> 
> > For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mpir-devel+unsubscr...@googlegroups.com.
To post to this group, send email to mpir-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/mpir-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to