similar to: methods:::.selectSuperClasses and byte compilation

Hello, Due to exploration of the JIT capabilities offered through the {compiler} package, I came by the fact that using enableJIT(2) can *slow* the rpart function (from the {rpart} package) by a magnitude of about 10 times. Here is an example code to run: library(rpart) require(compiler) enableJIT(0) # just making sure that JIT is off # We could also use enableJIT(1) and it would be fine fo

Hi, we have installed R-2.8.1 using the current pgi compiler (8.0.2) for AMD64 on a SLES9 system. When I try to install "Matrix" everything is fine until the last step. make[1]: Leaving directory `/tmp/R.INSTALL.TW3399/Matrix/src/AMD' pgCC -L/usr/lib64 -L/usr/X11R6/lib64 -pgf90libs -o Matrix.so CHMfactor.o Csparse.o TMatrix_as.o Tsparse.o init.o Mutils.o chm_common.o

>>>>> Henrik Bengtsson >>>>> on Tue, 24 Sep 2019 11:42:13 -0700 writes [to me (as maintainer of 'Matrix') and allowed me to answer in public] : > I ran into a problem where 'R CMD check' on my in-house package, which > only indirectly depends on 'Matrix', produce errors like: > > [where=<environment: namespace:Matrix>,

64-bit R-2.12.0 was installed on Sun SPARC Solaris 10. Compiler used is solstudio12.2. Attached is the configure script. I then tried to install a recommended package called Matrix. The compilation failed with the following messages, ....... CC -library=stlport4 -G -L/opt/csw/lib/sparcv9 -L/opt/solstudio12.2/prod/lib/v9 -o Matrix.so CHMfactor.o Csparse.o TMatrix_as.o Tsparse.o init.o Mutils.o

Thanks for the report. Fixed in R_devel with r72631; I'll port to R-patched later today or tomorrow. The default setting and how to get the current settings are documented in the Details section of the enableJIT help page at the end of the paragraph for enableJIT. Best, luke On Wed, 26 Apr 2017, Herv? Pag?s wrote: > Hi, > > I'm running into a case where byte-compilation

I'm exploring pedigree() in lme4 and found some strange results trying to multiply a dtCMatrix by a diag() matrix using %*%. Studying the Matrix documentation, I stumbled upon the following error in the example on the ddiMatrix-class {Matrix} help page. I wonder if my problem could be related to this. > matrix(cbind(1, 2:4),3,2) %*% diag(c(10,1)) # OK [,1] [,2] [1,] 10 2 [2,]

I need to perform a QR-decomposition of a sparse matrix, so I've been trying to use the Matrix package. Unfortunately I don't seem to be getting exactly the same results as if I had used the qr() command from the base package. Here is an example of what I'm doing. > spdata <-rpois(50,1) > y <- rnorm(10,0,1) > S <-

Dear Developers, motivated by the new Sun Studio checks I compiled R-devel and several of our packages with Sun Studio 12 on Fedora x64. Everything worked fine and R-devel runs, with the exception of package Matrix where compilation crashes with the following message. The error occurs during building of the recommended packages and also if Matrix is compiled separately: [...] CC -G -lCstd

A commenter on SO suggested that I copy my question to R-devel http://stackoverflow.com/q/31972325/850781 I have had --8<---------------cut here---------------start------------->8--- library(compiler) compiler::enableJIT(3) --8<---------------cut here---------------end--------------->8--- in ~/.Rprofile for years; now that I upgraded to 3.2.1 I get this on startup:

It looks like the byte compiler is optimizing local() to an immediately-invoked function, instead of using eval() and substitute(). I don't know if that's exactly how it's implemented internally, but that's what it looks like here: compiler::enableJIT(0) fun <- function(x) { local(sys.calls()) } fun(1) ## [[1]] ## fun(1) ## ## [[2]] ## local(sys.calls()) ## ## [[3]] ##

On 26/04/2017 4:36 PM, Herv? Pag?s wrote: > Hi, > > I'm running into a case where byte-compilation changes > the semantic of a function. This is with R 3.4.0: > > foo <- function(x) { TRUE && x } > > foo(c(a=FALSE)) > # [1] FALSE # OK > > foo(c(a=TRUE)) > # [1] TRUE # OK > > foo(c(a=FALSE)) > #

Hi all, I have trouble to compile Matrix packages on Solar10 x86-64 with Sun compilers. I saw some postings on this but am not sure how to solve this problem. It is becoming critical as I cannot install biocLite() because of its dependency on Matrix. Could you direct me how to resolve the issue? Thanks in advance! Dongseok R version 2.8.1 (2008-12-22) Copyright (C) 2008 The R Foundation for

I'm not sure if this is a bug or expected behavior, but I don't see anything in the documentation that explains it, so I thought I'd mention it: ~ michaelweylandt$ R -q --vanilla library(compiler) enableJIT(3) `+` # Throws an error `+` # Throws a warning `+` # Prints the primitive as expected sessionInfo() R version 2.14.1 (2011-12-22) Platform: i386-apple-darwin9.8.0/i386

Hi, Browser doesn't work properly with the compiler enabled. It might be intended behavior, but it's not documented. compiler::enableJIT(1) foo <- function(){ browser() cat("here\n") } Browser doesn't stop, and I am getting: > foo() Called from: foo() Browse[1]> here > Thanks, Vitalie. > sessionInfo() R version 2.14.2 (2012-02-29) Platform:

Dear list, I came across the following error for three of my newly written Rd-files: non-ASCII input and no declared encoding I can't make sense of this. Below I copied in one of the three files. Can anybody please tell me what's wrong with it? Thank you, Christian \name{tetragonula} \alias{tetragonula} \alias{tetragonula.coord} \docType{data} % \non_function{} \title{Microsatellite

Hi, I'm running into a case where byte-compilation changes the semantic of a function. This is with R 3.4.0: foo <- function(x) { TRUE && x } foo(c(a=FALSE)) # [1] FALSE # OK foo(c(a=TRUE)) # [1] TRUE # OK foo(c(a=FALSE)) # a # ???? # FALSE The 3rd call returned a result that it different from the 1st call! After

Dear list members, If I install with R-devel r74500 on Windows (sessionInfo below) the attached 'bugdemo' package with the single function foo <- function() { ? named <- c("bar"=TRUE) ? print(named) ? return(named) } then run > bugdemo::foo() [1] TRUE [1] TRUE The "bar" name is lost. It is not lost when I define foo in the R session instead of using

Thanks. This should be resolved in R-devel(r72788) and R-patched (r72789) Best, luke On Mon, 12 Jun 2017, Berend Hasselman wrote: > > > In this email to the R-help list: https://stat.ethz.ch/pipermail/r-help/2017-June/447474.html > and in this question on Stackoverflow: https://stackoverflow.com/questions/44486643/nleqslv-memory-use-in-r > > Andrew Leach has raised a question

I noticed some problems that cropped in the latest versions of R-devel (2016-11-08 r71639 in my case) for one of my packages. I _think_ I have narrowed it down to the changes to what gets byte-compiled by default. The following example run illustrates the problem I'm having: compiler::enableJIT(0) fun <- function(x) local(as.list(parent.frame(2))) fun(1) ## $x ## [1] 1 ##

Hi, I am running into a problem when I use the window<- replacement function in R 3.4.0. It will lead to an error when it is called inside a loop, probably the result of the byte compiler now enabled by default. When I turn it off, it works again, as in older versions of R. I tested on Win, Linux and Mac, and the problem occurs everywhere. Here is a reproducible example: z <-