Skip to content

Commit

Permalink
Merge branch 'tt2007/html_links'
Browse files Browse the repository at this point in the history
  • Loading branch information
jkeenan committed Aug 9, 2011
2 parents 70cca2a + 8402064 commit bb0b13f
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 49 deletions.
44 changes: 3 additions & 41 deletions docs/glossary.pod
Original file line number Diff line number Diff line change
Expand Up @@ -248,13 +248,8 @@ be added, or overridden (for instance, the PAST to PIR transformation).
Parrot Design Document: documents that describe the features parrot must
implement.

See also L<< http://github.com/parrot/parrot/docs/pdds/pdd00_pdd.pod.html >>.

=begin html

<a href="http://github.com/parrot/parrot/docs/pdds/pdd00_pdd.pod">pdd00_pdd.pod</a>

=end html
See also L<< Running|http://docs.parrot.org/parrot/latest/html/docs/running.pod.html >> and
L<< PDD 0: Design Document Format|http://docs.parrot.org/parrot/latest/html/docs/pdds/pdd00_pdd.pod.html >>.

=item PGE

Expand Down Expand Up @@ -302,49 +297,16 @@ See also L<"PCT">.

=item Predereferencing

=for comment
XXX This section needs to be edited down.

A bytecode transformation technique which reduces the amount of pointer
dereferencing done in the inner loop of the interpreter by pre-converting
opcode numbers into pointers to their opfuncs, and also converting the register
numbers and constant numbers in the arguments to the ops into pointers.

The original implementation by Gregor Purdy was posted on 2001-12-11. On one
test system, it resulted in a 22% speed increase on a test program with a tight
inner loop.

L<http://archive.develooper.com/perl6-internals@perl.org/msg06941.html>

On 2001-12-18, predereferencing got a speed boost (to about 47% faster than the
regular DO_OP inner loop -- without compiler optimizations turned on). This was
due to an off-list (actually over lunch) suggestion by John Kennedy that
instead of pre-initializing the new copy of the bytecode with NULL pointers, we
pre-initialize it with pointers to a pseudo-opfunc that does the
predereferencing whenever it is encountered.

On 2002-04-11, Jason Gloudon suggested combining aspects of the Computed Goto
Core and the Prederef[erencing] Core.

L<http://archive.develooper.com/perl6-internals@perl.org/msg07064.html>

The week of 2003-02-09, Leopold Toetsch combined Computed Goto and
Predereferencing to produce the CGP core.

L<http://dev.perl.org/perl6/list-summaries/2003/p6summary.2003-02-09.html#Week_of_the_alternative_runloops>

Later, on 2003-02-14, Leopold Totsch and Nicholas Clark combined the JIT and
the Computed Goto Prederef cores to great effect.

L<http://www.perl.com/pub/a/2003/02/p6pdigest/20030216.html>

=item run core

aka run loop, aka runcore. The way Parrot executes PBCs.
See running.pod for a list of available runcores, and how to tell
parrot which one to use.

running.pod: L<< https://github.com/parrot/parrot/parrot/docs/running.pod >>
parrot which one to use. L<< Running|http://docs.parrot.org/parrot/latest/html/docs/running.pod.html >>

=item SMOP

Expand Down
15 changes: 7 additions & 8 deletions docs/pct/gettingstarted.pod
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,13 @@ Getting Started with the Parrot Compiler Tools

=head1 DESCRIPTION

This document can be considered your Number One entry point for starting to use
the Parrot Compiler Tools (PCT). As there's a whole lot of acronyms flying
around (see Parrot's glossary at
L<https://github.com/parrot/parrot/blob/master/docs/glossary.pod>),
this document will get you up and running within 10 minutes (that excludes
building Parrot). Once you begin, it's a matter of getting your hands dirty and
get experienced using the tools. Feel free to ask questions in
the #parrot channel on irc.parrot.org .
This document can be considered your Number One entry point for starting to
use the Parrot Compiler Tools (PCT). There will be a whole lot of acronyms
flying around. Consult L<< Parrot's glossary|http://docs.parrot.org/parrot/latest/html/docs/glossary.html >> about
them. This document will get you up and running within 10 minutes (that
excludes building Parrot). Once you begin, it's a matter of getting your hands
dirty and get experienced using the tools. Feel free to ask questions in the
#parrot channel on irc.parrot.org .

=head1 GETTING STARTED

Expand Down

0 comments on commit bb0b13f

Please sign in to comment.