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
x86_64, acml-3.5.0-gfortran64 and lme4
2 messages · McGehee, Robert, James W. MacDonald
I am not encountering segfaults either, using earlier versions of gcc/gfortran64 (4.0.0) and acml (3.0.0) on a 64 bit build of R-2.4.0 on Fedora Core 4 Best, Jim
McGehee, Robert wrote:
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 ______________________________________________ R-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
James W. MacDonald Affymetrix and cDNA Core University of Michigan Cancer Center 1500 E. Medical Center Drive 7410 CCGC 734-647-5623 ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues.