Ignore:
Timestamp:
Mar 2, 2011, 2:19:42 PM (9 years ago)
Author:
mulligan
Message:

More work on slides.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • Deliverables/D1.1/Presentations/WP4-dominic-presentation.tex

    r617 r618  
    8686
    8787\begin{frame}
    88 \frametitle{Problems to be solved}
     88\frametitle{Dealing with the jumps}
     89\begin{itemize}
     90\item
     91Unconditional jumps a problem, as offset has to be computed ahead of time.
     92\item
     93This is problematic for separate compilation, and also for prototype C compiler.
     94\item
     95Much better to implement pseudoinstructions which are `assembled away'.
     96\item
     97Introduce labels and cost labels (for cost traces).
     98\item
     99Then introduce pseudoinstructions like \texttt{Jump} for unconditional jumping to labels: no offset calculation required beforehand.
     100\item
     101Other pseudoinstructions introduced: \texttt{Mov} for moving arbitrary (16 bit) data stored at a label (global vars) and conditional jumps to labels.
     102\item
     103Our assembly language similar to that of SDCC.
     104\end{itemize}
    89105\end{frame}
    90106
    91107\begin{frame}
    92108\frametitle{Polymorphic variants and phantom types}
     109\begin{itemize}
     110\item
     111The instruction set is highly non-orthogonal.
     112\item
     113We needed a way of
     114\end{itemize}
    93115\end{frame}
    94116
     
    97119\end{frame}
    98120
     121\begin{frame}
     122\frametitle{What is implemented}
     123In O'Caml we implemented the emulator proper, associated assembler, supprting debugging code (for loading and outputting Intel HEX), and also have (untested) code for timers, interrupts and I/O.
     124
     125In Matita, we have the emulator proper and associated assembler.
     126We have yet to port the timers and I/O, preferring to focus on the core emulator.
     127\end{frame}
     128
     129\begin{frame}
     130\frametitle{Demo}
     131\end{frame}
     132
    99133\end{document}
Note: See TracChangeset for help on using the changeset viewer.