From cb947dd005b0168dd719aa136d12c4c54a0b063c Mon Sep 17 00:00:00 2001 From: Scott Olson Date: Sun, 3 Apr 2016 23:25:30 -0600 Subject: [PATCH] Add note about target data layout. --- final-presentation/slides.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/final-presentation/slides.tex b/final-presentation/slides.tex index 892d31602c8..bd10c85b5a8 100644 --- a/final-presentation/slides.tex +++ b/final-presentation/slides.tex @@ -212,10 +212,6 @@ \end{itemize} \end{frame} -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -% Miri example slides -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% - \begin{frame}[fragile] \frametitle{\texttt{square} example} \begin{center} @@ -346,9 +342,12 @@ \item non-trivial casts \item function pointers \item calling destructors and freeing memory + \item taking target architecture endianess and alignment information + into account when computing data layout \item handling all constants properly (but, well, Miri might be replacing the old constants system) \end{itemize} + \pause \item Miri can't do foreign function calls (e.g. calling functions defined in C or C++), but there is a reasonable way it could be done with libffi. @@ -357,6 +356,7 @@ want the evaluator to be deterministic and safe, so FFI calls might be banned anyway. \end{itemize} + \pause \item Without quite some effort, Miri will probably never handle inline assembly...