The function cmpfun
compiles the body of a closure and
returns a new closure with the same formals and the body replaced by
the compiled body expression.
compile
compiles an expression into a byte code object; the
object can then be evaluated with eval
.
cmpfile
parses the expressions in infile
, compiles
them, and writes the compiled expressions to outfile
. If
outfile
is not provided, it is formed from infile
by
replacing or appending a .Rc
suffix.
loadcmp
is used to load compiled files. It is similar to
sys.source
, except that its default loading environment is the
global environment rather than the base environment.
disassemble
produces a printed representation of the code
that may be useful to give a hint of what is going on.
enableJIT
enables or disables just-in-time (JIT)
compilation. JIT is disabled if the argument is 0. If level
is
1 then larger closures are compiled before their first use. If
level
is 2, then some small closures are also compiled before
their second use. If level
is 3 then in addition
all top level loops are compiled before they are executed. JIT level
3 requires the compiler option optimize
to be 2 or 3. The JIT
level can also be selected by starting R with the environment
variable R_ENABLE_JIT
set to one of these values. Calling
enableJIT
with a negative argument returns the current JIT
level. The default JIT level is 3
.
compilePKGS
enables or disables compiling packages when they
are installed. This requires that the package uses lazy loading as
compilation occurs as functions are written to the lazy loading data
base. This can also be enabled by starting R with the environment
variable _R_COMPILE_PKGS_
set to a positive integer value.
This should not be enabled outside package installation, because it
causes any serialized function to be compiled, which comes with
time and space overhead. R_COMPILE_PKGS
can be used, instead,
to instruct INSTALL
to enable/disable compilation of packages
during installation.
Currently the compiler warns about a variety of things. It does
this by using cat
to print messages. Eventually this should
use the condition handling mechanism.
The options
argument can be used to control compiler operation.
There are currently four options: optimize
, suppressAll
,
suppressUndefined
, and suppressNoSuperAssignVar
.
optimize
specifies the optimization level, an integer from 0
to 3
(the current out-of-the-box default is 2
).
suppressAll
should be a scalar logical; if TRUE
no messages
will be shown (this is the default). suppressUndefined
can be
TRUE
to suppress all messages about undefined variables, or it can
be a character vector of the names of variables for which messages should
not be shown. suppressNoSuperAssignVar
can be TRUE
to
suppress messages about super assignments to a variable for which no
binding is visible at compile time. During compilation of packages,
suppressAll
is currently FALSE
, suppressUndefined
is
TRUE
and suppressNoSuperAssignVar
is TRUE
.
getCompilerOption
returns the value of the specified option.
The default value is returned unless a value is supplied in the
options
argument; the options
argument is primarily for
internal use. setCompilerOption
sets the default option
values. Options to set are identified by argument names, e.g.
setCompilerOptions(suppressAll = TRUE, optimize = 3)
.
It returns a named list of the previous values.
Calling the compiler a byte code compiler is actually a bit of a
misnomer: the external representation of code objects currently uses
int
operands, and when compiled with gcc
the internal
representation is actually threaded code rather than byte code.