Displaying 4 results from an estimated 4 matches for "dpotrs_".
Did you mean:
dpotrf_
2005 Jan 25
2
about R CMD check
...ibs
gcc -I/usr/lib/R/include -I/usr/local/include -D__NO_MATH_INLINES -mieee-fp
-fPIC -O2 -g -march=i386 -mcpu=i686 -c 1221.c -o 1221.o
1221.c: In function `Matrix_A_12':
1221.c:773: warning: passing arg 3 of `dpotrf_' from incompatible pointer type
1221.c:774: warning: passing arg 4 of `dpotrs_' from incompatible pointer type
1221.c: In function `Matrix_A_1':
1221.c:1037: warning: passing arg 3 of `dpotrf_' from incompatible pointer type
1221.c:1038: warning: passing arg 4 of `dpotrs_' from incompatible pointer type
1221.c: In function `Matrix_A_2':
1221.c:1289: warnin...
2005 Mar 10
1
about R CMD check
...lib/R/include -I/usr/local/include -D__NO_MATH_INLINES -mieee-fp
-fPIC -O2 -g -march=i386 -mcpu=i686 -c wxt1221.c -o wxt1221.o
wxt1221.c: In function `Matrix_A_12':
wxt1221.c:774: warning: passing arg 3 of `dpotrf_' from incompatible pointer
type
wxt1221.c:775: warning: passing arg 4 of `dpotrs_' from incompatible pointer
type
wxt1221.c: In function `Matrix_A_1':
wxt1221.c:1038: warning: passing arg 3 of `dpotrf_' from incompatible pointer
type
wxt1221.c:1039: warning: passing arg 4 of `dpotrs_' from incompatible pointer
type
wxt1221.c: In function `Matrix_A_2':
wxt1221...
2019 May 03
0
R problems with lapack with gfortran
...????????????? pop??? %r13
? 117509:?????? 41 5e?????????????????? pop??? %r14
? 11750b:?????? 41 5f?????????????????? pop??? %r15 <=== restore register to level before call
???????? CALL DPOTRS( UPLO, N, NRHS, A, LDA, B, LDB, INFO )
? 11750d:?????? e9 de 56 ef ff????????? jmpq?? cbf0 <dpotrs_ at plt> <=== tail call to dpotrs
Note that DPOSV never uses the length of the string (UPLO) from the
hidden argument, the compiler clearly knows that its length is 1. In
calls where the length is passed in registers, this does not cause
trouble (like LSAME) and indeed is needed as the reg...
2019 Apr 24
2
R problems with lapack with gfortran
Hi,
I have tried to pinpoint potential problems which could lead to the
LAPACK issues that are currently seen in R. I built the current R
trunk using
AR=gcc-ar RANLIB=gcc-ranlib ./configure --prefix=$HOME --enable-lto
--enable-BLAS-shlib=no --without-recommended-packages
and used this to find problem areas.
There are quite a few warnings that were flagged, due to mismatches
in function