similar to: optimized BLAS

I've been updating the information on tuned BLAS for R-admin in R-patched and R-devel. We have ATLAS (widely available, including for Windows) MKL (licensed on ix86 and x86_64 Linux and Windows) ACML (by AMD, but for all ix86 and x86_64 chips, Linux and Windows. Now available for gfortran.) Goto (academic use only, only some chips, only Linux) MKL and ACML provide full LAPACK,

I have problems building R 2.11.1 with an external BLAS. I've tried several with several libraries: # ACML: export LD_LIBRARY_PATH=/site/VERSIONS/acml-3.6.0/gfortran64_int64/lib BLAS=--with-blas="-L/site/VERSIONS/acml-3.6.0/gfortran64_int64/lib -lacml" LAPACK=--with-lapack # MKL 11: BLAS=--with-blas="-L/site/VERSIONS/intel-11.1/mkl/lib/em64t -lmkl_gf_lp64 -lmkl_sequential

In practical terms, failing tests are not preventing anyone from using an optimized BLAS/LAPACK implementation they trust. Building R with dynamically linked BLAS on Unix is supported, documented and easy for anyone who builds R from source. It is also how Debian/Ubuntu R packages are built by default, so R uses whichever BLAS is installed in the system and the user does not have to build

On Mon, Aug 29, 2005 at 11:48:23AM +0100, Prof Brian Ripley wrote: > On Mon, 29 Aug 2005, G?ran Brostr?m wrote: > >LAPACK/BLAS routines call xerbla "if an input parameter has an > >invalid value" (exact quote from XERBLA at Netlib). Other types of errors > >are not printed (by xerbla), but it is up to the user to check the return > >value of the argument

Greetings - For a host of reasons I chose (was forced) to upgrade my multi-Opteron box from Fedora 7 -> Fedora 8. In the process, I also updated the ACML I had installed from 4.0.0 to 4.1.0. While I get no errors (that I can find) in the config -> make -> make install sequence, I'm pretty sure (based on some benchmarks) that I'm not getting BLAS and/or Lapack to compile in. So,

Dear all, I am currently trying to link R 2.1.0 to the GOTO BLAS 0.99.3 library on a box running Fedora Core 3 , basically following the steps indicated in the R-Admin document: 1: I downloaded the current libgoto.xxx.so from http://www.cs.utexas.edu/users/kgoto/libraries/libgoto_prescott-32-r0.99-3.so.gz, a version suitable for our XEON machine (Nocona core), unpacked it to /usr/lib and created

Greetings - A quick perusal of some of the posts to this maillist suggest the level of the questions is probably beyond someone working at my level, but at the risk of looking foolish publicly (something I find I get increasingly comfortable with as I get older), here goes: My research group recently purchased a multi-Opteron system (bunch of 880 chips), running 64-bit RHEL 4 (which we have

>>>>> Tomas Kalibera <tomas.kalibera at gmail.com> >>>>> on Fri, 5 Jan 2018 00:41:47 +0100 writes: > In practical terms, failing tests are not preventing anyone from using > an optimized BLAS/LAPACK implementation they trust. Building R with > dynamically linked BLAS on Unix is supported, documented and easy for > anyone who

Well, CentOS 5.3, which amounts to the same thing. I recently decided to upgrade my main research machine from Fedora Core 8 -> CentOS 5.3. Basically, I was looking to move to a distro with longer 'term-of-life' than the release schedule for Fedora currently allows. The machine is a multi-Opteron box, so both 32- and 64-bit apps natively supported. Since I do a lot of 'linear

Hi Tomas, Thanks for your reply. I find your response curious, however. Surely the identical() test is simply incorrect when catering for possibly different BLAS implementations? Or is it the case that conformant BLAS implementations all produce bit-identical results, which seems unlikely? (Sorry, I am unfamiliar with the BLAS spec.) Although whatever the answer to this theoretical question,

Dear R-help, Here's a posting to the most recent NA-digest: From: Robert van de Geijn <rvdg at cs.utexas.edu> Date: Fri, 13 Dec 2002 11:15:23 -0600 Subject: Fast BLAS Libraries for Current Architectures Recent research by Kazushige Goto, Visiting Scientist at UT-Austin, has resulted in high-performance BLAS libraries for the Intel (R) Pentium (R) III and 4 processors, the

dear experts I'd like to ask you, probably on behalf all of us who try to use AMD's ACML for performance optimisation a question. There seem to be problem when these two, R and ACML are coupled, described here: http://devgurus.amd.com/message/1255852#1255852 I'd like to ask, while not being a programmer/developer, how incorrect and dangerous this might be? maybe such a setup must

Hello. I am a Linux neophyte and know almost nothing ?about compiling, so I would appreciate any help and advice y'all would care to offer. I am trying to compile the 64 bit version of R using a tuned ATLAS and LAPACK (ATLAS 3.9.24). I am running Ubunto 10.04 LTS (through wubi, FWIW). The ATLAS and LAPACK files (atlas.so, f77blas.so, lapack.so, and cblas.so) are sitting in the folder

I am encountering segfaults when checking the lme4 package on an Athlon64 system if I use the acml blas. R was built as a 64-bit application using the GCC 4.0.3 compiler suite including gfortran. The version of acml is 3.5.0 gfortran64. I do not encounter the segfaults when I compile R with R's built-in BLAS. The errors occur in the first example in lme4 in a call to lmer. It looks like

Hi, Has anyone had any luck in using portland group compiler to build R(-devel) with AMD's pgi compiled ACML library? I've downloaded the packages and set LD_LIBRARY_PATH, and run configuration script as follow: % ./configure --prefix=/usr/local/R.pgcc --with-blas='-lacml' However, it failed to pick up double complex BLAS, checking for sgemm_ in -lacml... yes checking

Hi, I am writing code interfacing R's BLAS functions, and have a problem with two missing const's in the header of F77_NAME(dger) in src/include/R_ext/BLAS.h. The current definition is missing the appropriate consts for the arrays x and y, which are stated in the BLAS documentation [2] to be "unchanged on exit". This issue was already mentioned on the list in March 2009 [1],

Normally, I do the following to configure R for compilation on my Opteron box with ACML installed: ./configure --with-tcltk --with-blas="-L/opt/acml4.3.0/gfortran64/lib -lacml" However, when I do so, and look at Makeconf, I see BLAS_LIBS = -lblas I thought I would see BLAS_LIBS = -L/opt/acml4.3.0/gfortran64/lib -lacml Why isn't Makeconf picking up the right BLAS_LIBS (or is

I'm trying to build R-devel with AMD's ACML. I downloaded version 3.0.0 64bit for gfortran (acml-3-0-0-gfortran-64bit.tgz) and copied the libraries to /usr/local/lib. When I configure R to build against the ACML library, how do I know if the library has been detected and will be used? I run 'configure' with the '--with-blas=-lacml' flag and am using gcc 4.0.2 (with

Greetings - I'm trying to compile R under GNU/Linux (RHEL 4) on a multi-Opteron box, with ACML support. First, I downloaded and installed ACML 3.5 - GNU version, although I'm not entirely sure what the differences are - from the AMD website. The ACML libraries were installed to /opt/acml3.5.0/ Second, I ran ./configure --with-blas='-lacml' The configure went fine,

So, I tried the following configure: ./configure --with-lapack --with-blas --with-tcltk No use of ACML at all, but both lapack and blas. Configure proceeds without any errors. Make, same thing. Make check - same problem with stats. But, this time a .fail file got created in tests/Example. Bottom of the file has something which might resonate with someone out there: Error in La.svd(x, nu,