search for: incx

...quot;R_ext/BLAS.h" void testzdotc() { Rcomplex zx[3], zy[3], ret_val; zx[0].r = 1.0; zx[0].i = 0.0; zx[1].r = 2.0; zx[0].i = 0.0; zx[2].r = 3.0; zx[0].i = 0.0; zy[0].r = 1.0; zy[0].i = 0.0; zy[1].r = 2.0; zy[0].i = 0.0; zy[2].r = 3.0; zy[0].i = 0.0; int n=3, incx=1, incy=1; F77_CALL(zdotc)(&ret_val, &n, zx, &incx, zy, &incy); Rprintf("ret_val = %f, %f\n", ret_val.r, ret_val.i); } This does not work. When I run '.C('testzdotc')' there is typically a delay for a second or so, then I get: 0.0, 0.0 instead of t...

...qualifiers from pointer target type the netlib documentation states that the arguments x and y should be unchanged on exit. Should should imply the defintion: F77_NAME(dger)(const int * const m, const int * const n, const double * const alpha, double const * const x, const int *const incx, double const * const y, const int *const incy, double * const a, const int * const lda); the current definition is missing the appropriate consts: F77_NAME(dger)(const int *m, const int *n, const double *alpha, double *x, const int *incx, double *y, con...

...posteriorL pL <- posteriorL pR <- posteriorR certState = gamma * certState + (1 - gamma) * pL thList[i] = ifelse(certState > 0.55, 1, ifelse(certState < 0.45, 0, ifelse(pL > 0.5, 1, 0))) } return(thList) } thesum=0 j = 1 minx = 0.01; maxx = 0.5; incx = 0.05; x = seq(minx, maxx, incx) miny = 0.0; maxy = 1; incy = 0.05; y = seq(miny, maxy, incy) for (i in x) { for (e in y) { thresholded = calc.probs(i, e) diff <- abs(dat2$choice - Lag(thresholded)) diff = ifelse(is.na(diff), 0, diff) thesum[j] = sum(diff, na.rm = T...

...ans, int *na, int *nw, double *smin, double *ca, double *a, int *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...

...s using the same linkage conventions (those of pcc) whereas users of other platforms are used to the idea that code from different compilers cannot in general be mixed. This is no longer true for gfortran on AMD64. Given a double complex function like double complex function zdotc(n,zx,incx,zy,incy) gfortran returns the result in a 128-bit XMM SSE register, whereas g77 (and gcc using Rcomplex) would return the result in memory. The result is that a BLAS compiled with g77 or gcc is not compatible with R compiled with gfortran and attempts to use the combination results in memory c...

I wanted a function that would give the euclidean distance of a vector. Then I was happy, because I found vecnorm listed on pg 55 of V&R (3rd edn) which I had just bought today. Then I was sad, because R did not have vecnorm. Then I was happy again, because I bethought myself that I could copy the function vecnorm from splus to my code. Then I was sad again because R complained >

...w x2 Now, the question is, why do we need "mul (i64 vscale, i64 4)" in the IR? There is no semantic analysis you can do on a value that can change on every iteration of the loop. You can't elide, hoist, combine or const fold. If I got it right (from random documents on the web), `incX` relates to a number of "increment induction" functionality. `incw` is probably "increment W", ie. 32-bits, while `incp` is "increment predicate", ie. whatever the size of the predicate you use: Examples: incw x2 # increments x2 to 4*(FFR successful lanes)...

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

Followup: I have checked my package nleqslv which uses dgemv only from Fortran, on Kubuntu 18.04 with the development version of R. No errors or problems. Berend > On 12 Sep 2019, at 08:57, Berend Hasselman <bhh at xs4all.nl> wrote: > > > I have tried what I proposed in a virtual Kubuntu 18.04 which uses gfortran 7.4. > I used the latest development version of R. >

Hi Renato, Sorry for the delay in responding. We've been busy rethinking some of our changes after the feedback we've received thus far (particularly from the devmeeting). The incremental patches will use our revised design(which should be less invasive), and I'll be updating our document to match. On 16/11/2016, 12:46, "Renato Golin" <renato.golin at linaro.org>