-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I am using numpy-1.0.1 and ran into problems with 4 routines in
lapack_litemodule.c on 64 bit machines. Traced it back to parsing of
ints as longs. This has been fixed in numpy-1.0.3 for three of the
routines. lapack_lite_zgeqrf() still has the wrong parsing though. The
attached patch should fix it, I guess.

Ă–ssi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGXpPIHbjsBy8IXVsRAnIEAJ0c6ln97VUI/CYl2O9IfbQD+2eOXQCgjxRE
kVfuLQrDk4k5hTzqaBMj9Qw=
=SVBu
-----END PGP SIGNATURE-----
--- lapack_litemodule.c	2007-03-11 07:34:55.000000000 +0100
+++ lapack_litemodule.c_fixed	2007-05-31 11:12:26.000000000 +0200
@@ -755,7 +755,7 @@
         int lda;
         int info;
 
-        TRY(PyArg_ParseTuple(args,"llOlOOll",&m,&n,&a,&lda,&tau,&work,&lwork,&info));
+        TRY(PyArg_ParseTuple(args,"iiOiOOii",&m,&n,&a,&lda,&tau,&work,&lwork,&info));
 
 /* check objects and convert to right storage order */
         TRY(check_object(a,PyArray_CDOUBLE,"a","PyArray_CDOUBLE","zgeqrf"));
@@ -765,7 +765,7 @@
         lapack_lite_status__ = \
         FNAME(zgeqrf)(&m, &n, ZDATA(a), &lda, ZDATA(tau), ZDATA(work), &lwork, &info);
 
-        return Py_BuildValue("{s:l,s:l,s:l,s:l,s:l,s:l}","zgeqrf_",lapack_lite_status__,"m",m,"n",n,"lda",lda,"lwork",lwork,"info",info);
+        return Py_BuildValue("{s:i,s:i,s:i,s:i,s:i,s:i}","zgeqrf_",lapack_lite_status__,"m",m,"n",n,"lda",lda,"lwork",lwork,"info",info);
 }


_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion

Reply via email to