Displaying 3 results from an estimated 3 matches for "normin".
Did you mean:
norman
2019 May 11
1
R problems with lapack with gfortran
...*lda, double *d1, double *d2, double *b, int
*ldb, double *wr, double *wi, double *x, int *ldx, double *scale, double
*xnorm, int *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...
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
2005 Jun 21
9
[OT] Memory Models and Multi/Virtual-Cores -- WAS: 4.0 -> 4.1 update failing
From: Maciej ?enczykowski <maze at cela.pl>
> That's a good point - does anyone know what the new Intel
> Virtualization thingamajig in the new dual core pentium D's is about?
It's all speculation at this point. But there are _several_ factors.
But I'm sure the first time Intel saw AMD's x86-64/PAE52 presentation,
the same thing popped into my mind that popped