Displaying 2 results from an estimated 2 matches for "diag_len".
2019 May 11
1
R problems with lapack with gfortran
...*info);
void dlabad_ (double *small, double *large);
void drscl_ (int *n, double *sa, double *sx, int *incx);
void dlatrs_ (char *uplo, char *trans, char *diag, char *normin, int *n,
double *a, int *lda, double *x, double *scale, double *cnorm, int *info,
size_t uplo_len, size_t trans_len, size_t diag_len, size_t normin_len);
which could serve as the basis for adjusting the calling sequence
for the C bindings to what the compiler expects.
I checked, and it appears that at least ifort uses the same convention
as gfortran 8/9 regarding character argument passing.
Regards
Thomas
2019 May 04
4
R problems with lapack with gfortran
On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas K?nig wrote:
>
> > - figure out Fortran2003 specification for C/Fortran interoperability
> > -- this _sounds_ like the right solution, but I don't think many
> > understand how to use it and what is implied (in particular, will
> > it require making changes to LAPACK itself?)
>
> That would actually be fairly