Re: [Numpy-discussion] (apparent) infinite loop in LAPACK/ATLAS
On Wed, Nov 4, 2009 at 2:55 PM, David Warde-Farley d...@cs.toronto.edu wrote: Hi all (mostly David C. since he probably knows all this horrible stuff), I noticed on my new laptop (with an Atom N280 in it) that when I run numpy.test() about the 34th test would loop, seemingly forever. Finding this a little odd, I tried an SVD on a small matrix and observed the same behaviour, narrowed it down with gdb to what seems to be an infinite loop involving dlamc1_ and dlamc3_, Did you compile them without any optimized as suggested in the makefiles ? NOOPT should not contain -O option David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] (apparent) infinite loop in LAPACK/ATLAS
Hi David, On 4-Nov-09, at 4:23 AM, David Cournapeau wrote: Did you compile them without any optimized as suggested in the makefiles ? NOOPT should not contain -O option Yup, it contained -O0 -fPIC (-O0 I think is in fact more strict than having no -O option?). Have you seen this problem with broken NOOPT? I'm not certain yet, but it looks like some combination of gcc 4.4 and the Atom microarchitecture reintroduces this old bug, as -ffloat- store seems to have fixed it. numpy.test() runs through just fine once I recompiled LAPACK and then ATLAS as well (just rebuilding the lapack_LINUX.a and then running 'make' in the ATLAS obj dir didn't seem to do it, so I had to wait through several hours of tuning again). For anyone who might stumble upon this problem again, just to be safe I added -ffloat-store to both the flag lists in LAPACK's make.inc, and also used -Fa fi '-ffloat-store' when running configure with ATLAS. If this is indeed either a gcc 4.4 regression or an Atom-specific quirk it might start popping up more and more around here. David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] (apparent) infinite loop in LAPACK/ATLAS
Hi all (mostly David C. since he probably knows all this horrible stuff), I noticed on my new laptop (with an Atom N280 in it) that when I run numpy.test() about the 34th test would loop, seemingly forever. Finding this a little odd, I tried an SVD on a small matrix and observed the same behaviour, narrowed it down with gdb to what seems to be an infinite loop involving dlamc1_ and dlamc3_, which I gather are routines for converting from row-major to column-major. I should mention that I built ATLAS (3.9.7, because that's the tarball I had around) and LAPACK (3.1.1) from source. Oh, and this is on Ubuntu 9.10, Karmic Koala, using gcc 4.4.1 (with the exception of the ATLAS kernels which are using gcc 4.2.4 for the reasons stated in the install document). I came upon this mention of a similar problem ( https://projects.coin-or.org/BuildTools/ticket/66 ), so far. I'm going to try using the flag they suggest but it'll be a while before I have a verdict on whether it's fixed or not, so I'm soliciting any other ideas as to the cause of/solution to such an issue. Thanks in advance, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
