[pypy-commit] extradoc extradoc: start the talk

[cfbolz]

Author: Carl Friedrich Bolz <cfbolz at gmx.de>
Branch: extradoc
Changeset: r4844:2ef0495805d7
Date: 2012-10-09 16:07 +0200
http://bitbucket.org/pypy/extradoc/changeset/2ef0495805d7/

Log:	start the talk

diff --git a/talk/vmil2012/presentation/talk.tex b/talk/vmil2012/presentation/talk.tex
new file mode 100644
--- /dev/null
+++ b/talk/vmil2012/presentation/talk.tex
@@ -0,0 +1,123 @@
+\documentclass[utf8x]{beamer}
+
+% This file is a solution template for:
+
+% - Talk at a conference/colloquium.
+% - Talk length is about 20min.
+% - Style is ornate.
+
+\mode<presentation>
+{
+  \usetheme{Warsaw}
+  % or ...
+
+  %\setbeamercovered{transparent}
+  % or whatever (possibly just delete it)
+}
+
+
+\usepackage[english]{babel}
+\usepackage{listings}
+\usepackage{ulem}
+\usepackage{color}
+\usepackage{alltt}
+
+\usepackage[utf8x]{inputenc}
+
+
+\newcommand\redsout[1]{{\color{red}\sout{\hbox{\color{black}{#1}}}}}
+
+% or whatever
+
+% Or whatever. Note that the encoding and the font should match. If T1
+% does not look nice, try deleting the line with the fontenc.
+
+
+\title{The Efficient Handling of Guards in the Design of RPython's Tracing JIT}
+
+\author[David Schneider, Carl Friedrich Bolz]{David Schneider \and \emph{Carl Friedrich Bolz}}
+% - Give the names in the same order as the appear in the paper.
+% - Use the \inst{?} command only if the authors have different
+%   affiliation.
+
+\institute[Heinrich-Heine-Universität Düsseldorf]{
+Heinrich-Heine-Universität Düsseldorf, STUPS Group, Germany
+}
+
+\date{2012 VMIL, XXX}
+% - Either use conference name or its abbreviation.
+% - Not really informative to the audience, more for people (including
+%   yourself) who are reading the slides online
+
+
+% If you have a file called "university-logo-filename.xxx", where xxx
+% is a graphic format that can be processed by latex or pdflatex,
+% resp., then you can add a logo as follows:
+
+
+
+
+% Delete this, if you do not want the table of contents to pop up at
+% the beginning of each subsection:
+%\AtBeginSubsection[]
+%{
+%  \begin{frame}<beamer>
+%    \frametitle{Outline}
+%    \tableofcontents[currentsection,currentsubsection]
+%  \end{frame}
+%}
+
+
+% If you wish to uncover everything in a step-wise fashion, uncomment
+% the following command: 
+
+%\beamerdefaultoverlayspecification{<+->}
+
+
+\begin{document}
+
+\begin{frame}
+  \titlepage
+\end{frame}
+
+% XXX todos:
+% note that two fields is a simplification
+% have a diagram for the example trace
+% lifting can never produce new operations
+% have some sort of overview or position indicator for the many graphical slides, too easy to get lost
+% more details about benchmarks, diagram?
+
+
+% Structuring a talk is a difficult task and the following structure
+% may not be suitable. Here are some rules that apply for this
+% solution: 
+
+% - Exactly two or three sections (other than the summary).
+% - At *most* three subsections per section.
+% - Talk about 30s to 2min per frame. So there should be between about
+%   15 and 30 frames, all told.
+
+% - A conference audience is likely to know very little of what you
+%   are going to talk about. So *simplify*!
+% - In a 20min talk, getting the main ideas across is hard
+%   enough. Leave out details, even if it means being less precise than
+%   you think necessary.
+% - If you omit details that are vital to the proof/implementation,
+%   just say so once. Everybody will be happy with that.
+
+
+\begin{frame}
+  \frametitle{Tracing JITs Compile by Observing an Interpreter}
+  \begin{itemize}
+      \item VM contains both an interpreter and the tracing JIT compiler
+      \item JIT works by observing and logging what the interpreter does
+      \begin{itemize}
+          \item for interesting, commonly executed code paths
+          \item produces a linear list of operations (trace)
+      \end{itemize}
+      \item trace is optimized and then turned into machine code
+  \end{itemize}
+\end{frame}
+
+
+\end{document}