Displaying 3 results from an estimated 3 matches for "dgbmv".
2014 Jul 07
1
R with external BLAS fails regression test
...0559 compliance of an external BLAS. This can be broken if for
example the code assumes that terms with a zero factor are always zero
and do not need to be computed - whereas x*0 can be NaN. This is checked
in the test suite."
The version of BLAS that comes with R contains patched versions of
DGBMV, DGEMM, and DGEMV. The patch has been in place since 2010.
Presumably R blas and reference BLAS have been divergent ever since.
I guess this should be reported upstream as a BLAS bug. Recalling the
previous thread on openblas, I note that openblas does pass the
regression test.
Martyn
CC: Lejec...
2019 Apr 24
2
R problems with lapack with gfortran
...ed
by -Wlto-type-mismatch, which, for example, yields
print.c:1120:12: note: type 'void' should match type 'long int'
../../src/extra/blas/blas.f:357:20: warning: type of 'xerbla' does not
match original declaration [-Wlto-type-mismatch]
357 | CALL XERBLA( 'DGBMV ', INFO )
So, why can gcc's r268992 / r269349 matter? Before these patches,
gfortran used the variadic calling convention for calling procedures
outside the current file, and the non-variadic calling convention for
calling procedures found in the current file.
Because the procedures were...
2019 May 03
0
R problems with lapack with gfortran
...ch, which, for example, yields
>
> print.c:1120:12: note: type 'void' should match type 'long int'
> ../../src/extra/blas/blas.f:357:20: warning: type of 'xerbla' does not
> match original declaration [-Wlto-type-mismatch]
> ? 357 |????????? CALL XERBLA( 'DGBMV ', INFO )
>
>
> So, why can gcc's r268992 / r269349 matter? Before these patches,
> gfortran used the variadic calling convention for calling procedures
> outside the current file, and the non-variadic calling convention for
> calling procedures found in the current file....