Changeset 1205


Ignore:
Timestamp:
Sep 10, 2011, 12:16:54 PM (8 years ago)
Author:
mulligan
Message:

typographical changes

File:
1 edited

Legend:

Unmodified
Added
Removed
  • Deliverables/D4.1/ITP-Paper/itp-2011.tex

    r1204 r1205  
    6161\author{Dominic P. Mulligan \and Claudio Sacerdoti Coen}
    6262\authorrunning{D. P. Mulligan \and C. Sacerdoti Coen}
    63 \institute{\vspace{-2em}}
    64 % \institute{Dipartimento di Scienze dell'Informazione,\\ Universit\`a di Bologna}
     63\institute{Dipartimento di Scienze dell'Informazione,\\ Universit\`a di Bologna}
    6564
    6665\bibliographystyle{plain}
     
    9897The code that is actually run is not the high level source code that we reason on, but low level code generated by the compiler.
    9998
    100 Questions now arise:  What properties are preserved during compilation?
     99Questions now arise:
     100\begin{itemize*}
     101\item
     102What properties are preserved during compilation?
     103\item
    101104What properties are affected by the compilation strategy?
     105\item
    102106To what extent can you trust your compiler in preserving those properties?
     107\end{itemize*}
    103108These and other questions motivate a current `hot topic' in computer science research: \emph{compiler verification} (e.g.~\cite{chlipala:verified:2010,leroy:formal:2009}, and so on).
    104109So far, the field has only been focused on the first and last questions.
Note: See TracChangeset for help on using the changeset viewer.