Author: bernhard Date: Sun Oct 23 03:27:30 2005 New Revision: 9535 Modified: trunk/docs/glossary.pod trunk/docs/native_exec.pod Log: "make hello" gives example for creating native object from PASM, "make testexec" tries to run the RUNCORE test via the exex runcore.
Mention the term "run core" in glossary.pod. Modified: trunk/docs/glossary.pod ============================================================================== --- trunk/docs/glossary.pod (original) +++ trunk/docs/glossary.pod Sun Oct 23 03:27:30 2005 @@ -273,6 +273,13 @@ the Computed Goto Prederef cores to grea L<http://www.perl.com/pub/a/2003/02/p6pdigest/20030216.html> +=head2 run core + +aka run loop, aka runcore. The way Parrot executes Parrot Byte Code. +See L<running.pod> on how to tell parrot which run core should be used. + +=for TODO + Add a list of available run cores, or provide pointer to documentation. =head2 Vtable Modified: trunk/docs/native_exec.pod ============================================================================== --- trunk/docs/native_exec.pod (original) +++ trunk/docs/native_exec.pod Sun Oct 23 03:27:30 2005 @@ -14,8 +14,9 @@ engine and a precompiled Parrot program =head1 Generating a native executable Generating a native executable is done in three steps: building a packfile, -assembling a native object, and then linking the native executable. The -packfile is generated in the standard way from .imc or .pasm source by IMCC. +assembling a native object, and then linking the native executable. + +The packfile is generated in the standard way from .imc or .pasm source by IMCC. For a program in myprog.pasm: ./parrot -o myprog.pbc myprog.pasm @@ -36,15 +37,15 @@ This generates the "myprog" executable, minus the time required to JIT-compile the bytecode. -The "testexec" Makefile target demonstrates this method for a "Hello world" -program. +The "hello" target of the root Makefile demonstrates this method +for a "Hello world" program. =head1 Details =head2 Platform support The exec subsystem is enabled if support is determined automatically by -config/auto/jit.pl, or if --execcapable is explicitly specified to +config/auto/jit.pl, or if the option --execcapable is explicitly specified to Configure.pl. The platform must support the JIT core, and some additional scaffold in the exec* sources must be provided. Implementation of such is beyond the scope of this document. @@ -53,7 +54,7 @@ beyond the scope of this document. Native objects are generated by the "exec" run core. This core uses the JIT subsystem to compile a packfile to native instructions, then serializes it to -the platform's native object format. This object is then loaded at runtime and +the platform's native object format. This object is then loaded at runtime and executed using the normal JIT core. Unlike the standard cores (switch, computed goto, etc.) which are activated by
