[Rcpp-devel] Differences between RcppEigen and RcppArmadillo
cubranic at stat.ubc.ca
Tue Jun 19 05:47:00 CEST 2012
As I understand it, both Ra and the R 'compiler' package are bytecode
JITs, so roughly like Java '.class' and Emacs '.elc' files. There is no
current method that compiles R into machine code, which is what JIT in
the JVM does, and which is why Java does so well in the language
On 12-06-18 01:15 PM, Antonio Piccolboni wrote:
> Ooops, wrong JIT! Dirk is absolutely right. I meant to say see enableJIT
> is the compiler package, see
> I second Dirk's comments on Ra.
> On Mon, Jun 18, 2012 at 12:53 PM, Dirk Eddelbuettel <edd at debian.org
> <mailto:edd at debian.org>> wrote:
> On 18 June 2012 at 11:55, Antonio Piccolboni wrote:
> | On Sun, Jun 17, 2012 at 9:09 PM, c s <conradsand.arma at gmail.com
> <mailto:conradsand.arma at gmail.com>> wrote:
> | Another is
> | R. I believe R currently doesn't have a JIT compiler (I haven't
> | checked lately), and hence the very useful Rcpp fills in the
> | performance gap.
> | Still work in progress but see
> | Doesn't replace Rcpp by any stretch of the imagination, but may
> close the gap a
> | little bit.
> Sadly, Ra and jit are no longer maintained by Stephen Milborrow.
> I actually used to provided a patched binary for this within Debian.
> This was
> ahead of its time (ginve the renewed interest in JITs from LLVM and
> places) and quite useful, but Ra/jit is at this point a dead project.
> Dirk Eddelbuettel | edd at debian.org <mailto:edd at debian.org> |
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
More information about the Rcpp-devel