From Robert.McGehee at geodecapital.com  Mon Oct 16 17:00:06 2006
From: Robert.McGehee at geodecapital.com (McGehee, Robert)
Date: Mon, 16 Oct 2006 11:00:06 -0400
Subject: [Rd] x86_64, acml-3.5.0-gfortran64 and lme4
Message-ID: <67DCA285A2D7754280D3B8E88EB548020C946941@MSGBOSCLB2WIN.DMN1.FMR.COM>

I am not encountering segfaults on a 64-bit build of R 2.4.0 compiled
with gcc and g77 3.4.5 and ATLAS 3.6.0 on a Red Hat Athlon64 system.

-----Original Message-----
From: r-devel-bounces at r-project.org
[mailto:r-devel-bounces at r-project.org] On Behalf Of Douglas Bates
Sent: Monday, October 16, 2006 10:26 AM
To: R Development Mailing List
Subject: [Rd] x86_64, acml-3.5.0-gfortran64 and lme4

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 they would occur in any call to lmer.  Running
under the debugger shows that the segfault occurs in a call to dtrsm
(a level-3 BLAS routine to solve a triangular system of equations)
that is called from within a cholmod (sparse matrix library) routine.

Has anyone succeeded in running R CMD check on the lme4 package with
accelerated BLAS?  I'm trying to pin down is this occurs only with
ACML or also with Atlas and/or Goto's BLAS.

______________________________________________
R-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel




[Rd] x86_64, acml-3.5.0-gfortran64 and lme4
McGehee, Robert