[SciPy-dev] newscipy - special problems

Arnd Baecker arnd.baecker at web.de
Sat Oct 29 16:36:13 CDT 2005


On Sat, 29 Oct 2005, Travis Oliphant wrote:

> Arnd Baecker wrote:
>
> >      print *, " in ZBESH1 C"
> >      BB=DBLE(FLOAT(I1MACH(9)))*0.5D0
> >      print *, " in ZBESH1 D"
> >
> >
> Is the problem with i1mach?

I don't think so (at least not directly) as
 BB=I1MACH(9)
got me beyond that point.

> You could replace the line with
>
> BB=DBLE(2147483647)*0.5D0

also gets me beyond that point but
then gets a floating point exception when calling

      CALL ZBKNU(ZNR, ZNI, FNU, KODE, NN, CYR, CYI, NZ, TOL, ELIM, ALIM)
  (whose code contains similarly
     DBLE(FLOAT(I1MACH(14)-1)) - but I did not follow this further ...)

> or
>
> BB=DBLE(FLOAT(21477483647))*0.5D0

leads to:
                       ^
Integer at (^) too large
error: Command "/usr/bin/g77 -Wall -fno-second-underscore -fPIC -O3
-funroll-loops -march=pentium3 -mmmx -msse -fomit-frame-pointer
-malign-double -c -c Lib/special/amos/zbesh.f -o
build/temp.linux-i686-2.3/Lib/special/amos/zbesh.o" failed with exit
status 1

 > and see if that helps. > >

> The other problems may be ATLAS issues.

Though that ATLAS works fine with "old" scipy and the
corresponding debian packages. So I am not sure
what to do about it ...

> Yes, it could be compiler
> optimization problems.  Presumably distutils has a way to turn off
> compiler optimizations.

That would be the nicest solution, I'd guess.

> You could compile the amos library manually
> without compiler optimizations and just place it in the build/tempYYYYY/
> directory where it will be picked up by distutils.

I will have to leave that for tomorrow (if I find
a way how to do this - at first glance it was not obvious to me ...)

Best, Arnd




More information about the Scipy-dev mailing list