[pypy-svn] extradoc extradoc: merge
fijal
commits-noreply at bitbucket.org
Mon Apr 11 19:40:10 CEST 2011
Author: Maciej Fijalkowski <fijall at gmail.com>
Branch: extradoc
Changeset: r3495:4082a4379c58
Date: 2011-04-11 19:39 +0200
http://bitbucket.org/pypy/extradoc/changeset/4082a4379c58/
Log: merge
diff --git a/sprintinfo/gothenburg-2011/people.txt b/sprintinfo/gothenburg-2011/people.txt
--- a/sprintinfo/gothenburg-2011/people.txt
+++ b/sprintinfo/gothenburg-2011/people.txt
@@ -17,5 +17,6 @@
Antonio Cuni 26-30 Hotel Poseidon his own diet :)
Armin Rigo 23-02 SGS Veckobostader
Hakan Ardo 24-27 ???
+Romain Guillebert 23-03 ???
==================== ============== ===================== ==================
diff --git a/pypy.org/source/download.txt b/pypy.org/source/download.txt
--- a/pypy.org/source/download.txt
+++ b/pypy.org/source/download.txt
@@ -6,6 +6,12 @@
Download
============================================================
+.. class:: download_menu
+
+ There are `nightly binary builds`_ available. Those builds are not always
+ as stable as the release, but they contain Python 2.7 compatibility,
+ numerous bugfixes and performance improvements.
+
Here are the various binaries of **PyPy 1.4.1** that we provide for x86 Linux,
Mac OS/X or Windows. This is mostly a bugfix release, although the performance
over the previous release 1.4 has improved in some cases.
@@ -160,6 +166,7 @@
.. _`stackless`: http://www.stackless.com/
.. _`greenlets`: http://codespeak.net/svn/greenlet/trunk/doc/greenlet.txt
.. _Mercurial: http://mercurial.selenic.com/
+.. _`nightly binary builds`: http://buildbot.pypy.org/nightly/trunk/
Checksums
---------
diff --git a/pypy.org/source/README b/pypy.org/source/README
--- a/pypy.org/source/README
+++ b/pypy.org/source/README
@@ -1,14 +1,14 @@
-You generate this website by using yatiblog from here:
+You can get necessary software by doing:
-http://github.com/tav/ampify/blob/master/environ/yatiblog
+git clone https://github.com/tav/ampify.git
-by running
+and then recreate the website in this directory by running
-..../ampify/environ/yatiblog -o ..
+ampify/environ/yatiblog -o ..
you'll get html output in the parent directory.
Then you can check it in, go to codespeak in /www/pypy.org/htdocs/
-and type "svn up".
+and type "hg pull -u".
Other required dependencies:
* "docutils" from "easy_install docutils"
diff --git a/talk/icooolps2011/paper.tex b/talk/icooolps2011/paper.tex
--- a/talk/icooolps2011/paper.tex
+++ b/talk/icooolps2011/paper.tex
@@ -215,9 +215,6 @@
and less error prone than manually writing a JIT compiler. Similarly, writing
in a high level language such as RPython is easier than writing in C.
-XXX [fijal] yet another advantage is that JIT is by design supporting the whole
- language
-
We call the code that runs on top of an interpreter implemented with PyPy the
\emph{user code} or \emph{user program}.
@@ -264,7 +261,8 @@
Tracing through the execution of an interpreter has many advantages. It makes
the tracer, its optimizers and backends reusable for a variety of languages. The
language semantics do not need to be encoded into the JIT. Instead the tracer
-just picks them up from the interpreter.
+just picks them up from the interpreter. This also means that the JIT by
+construction supports the full language.
While the operations in a trace are those of the interpreter, the loops that are
traced by the tracer are the loops in the
@@ -783,10 +781,6 @@
class did not change since the trace was produced. It will fail if somebody
calls the \texttt{write\_method} method on the class.
-XXX [fijal] maybe it's worth noting that those guards are removed out of
- the loop by loop-invariant-code motion, unless our is so special
- we want to write a special paper about it
-
%___________________________________________________________________________
\subsection{Real-World Considerations}
@@ -880,8 +874,6 @@
all benchmarks, which is not surprising because CPython is a simple
bytecode-based interpreter.
-XXX [fijal] wouldn't a graph be better?
-
\begin{figure}
\begin{center}
{\footnotesize
diff --git a/pypy.org/download.html b/pypy.org/download.html
--- a/pypy.org/download.html
+++ b/pypy.org/download.html
@@ -47,6 +47,9 @@
<div>
<div id="main">
<h1 class="title">Download and install</h1>
+<p class="download-menu">There are <a class="reference external" href="http://buildbot.pypy.org/nightly/trunk/">nightly binary builds</a> available. Those builds are not always
+as stable as the release, but they contain Python 2.7 compatibility,
+numerous bugfixes and performance improvements.</p>
<p>Here are the various binaries of <strong>PyPy 1.4.1</strong> that we provide for x86 Linux,
Mac OS/X or Windows. This is mostly a bugfix release, although the performance
over the previous release 1.4 has improved in some cases.</p>
More information about the Pypy-commit
mailing list