On 6/24/07, rex <[EMAIL PROTECTED]> wrote:
- Charles R Harris < [EMAIL PROTECTED]> [2007-06-24 06:22]:
- >
- >
- > On 6/23/07, rex <[EMAIL PROTECTED]> wrote:
- >
- > Stefan van der Walt <[EMAIL PROTECTED]> [2007-06-23 15:06]:
- >>
- >> On Sat, Jun 23, 2007 at 07:35:35PM +0000, John Ollinger wrote:
- >>> I have just been updating our version of Python, numpy and
- >>> scipy and have run into a floating point exception that crashes
- >>> Python when I test the release.
- >
- > What do you mean by crash? Is anything printed? Do older versions of numpy
- > still work?
- John needs to respond to this.
- >>> I am running gcc 3.3.1 on SuSe Linux 2.4.21-144-smp4G. The error
- >>> first occurred with numpy-1.0.3. I downloaded svn 3875 when I then
- >>> read the scipy web page and installed the latest subversion. The
- >>> test command I am using is >>> python -c 'import numpy;
- >>> numpy.test(level=1,verbosity==2)' >>> and occurs during the matvec
- >>> test. This test uses rand to generate 10x8 and 8x1
- >>
- >> It may be worth checking whether the new version of numpy is picked
- >> up. You can do that using
- >>
- >> import numpy as N
- > > print N.__version__
- > >
- > > We have a build slave with a very similar setup to yours (see
- > > http://buildbot.scipy.org ) and everything seems to be fine.
- >
- > It's somewhat different:
- > SUSE 10.2
- > Core 2 Duo 32-bit
- > Kernel 2.6.18.2-34-default
- > gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)
- > Python 2.5 (r25:51908, Nov 27 2006
- > print N.__version__
- > 1.0.4.dev3868
- > python -c 'import numpy; numpy.test(level=1,verbosity=2)'
- > [...]
- > Ran 590 tests in 0.473s
- >
- >
- > Do you use Atlas? If so, did you compile it yourself or did you use a package?
- > There is a bug in some older 64 bit Atlas packages running on newer intel
- > hardware that generates illegal instruction exceptions and I am wondering if
- > you may have found a new 32 bit bug. One way to check this is to multiply two
- > big matrices together. There are many paths through Atlas, so the known bug is
- > not encountered in all matrix multiplications, and perhaps not for all floating
- > values either.
- The above system is running the http://buildbot.scipy.org/ buildbot with
- no errors. It doesn't appear to build ATLAS. It's John's older system
- (gcc 3.3.1 2.4.21-144-smp4G) -- AFAIK, 2.4.21 was used in SUSE
- 9.0. Current version is 10.2 -- that is throwing an error, not mine.
Sorry, my mistake. And I misread 2.4.21 as 2.6.21, a very recent kernel. Just shows how fast the years pass by.
Chuck
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
You hit the nail on the head. It is apparently an Atlas problem. I originally built numpy with optimized Atlas libraries. When I deleted these from the site.cfg file the problem went away.
I apologize for not including the error message in my initial post. Here it is in case anyone cares:
check_matvec (numpy.core.tests.test_numeric.test_dot)Floating point exception
I appreciate the helpful responses. I will fool around with Atlas to see if I can eliminate the problem. I have to do stuff that makes people want to pay for part of today, so I might not post again for a day or two.
Thanks again,
John
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
