Commit 2eed7245 authored by Jayke Meijer's avatar Jayke Meijer

Small changes report.

parent 95f32aab
...@@ -246,14 +246,18 @@ the generated Assembly code. ...@@ -246,14 +246,18 @@ the generated Assembly code.
The writer expects a list of statements, so first the blocks have to be The writer expects a list of statements, so first the blocks have to be
concatenated again into a list. After this is done, the list is passed on to concatenated again into a list. After this is done, the list is passed on to
the writer, which writes the instructions back to Assembly and saves the file the writer, which writes the instructions back to Assembly and saves the file
so we can let xgcc compile it. We also write the original statements to a file, so we can let xgcc compile it. The original statements can also written to a
so differences in tabs, spaces and newlines do not show up when we check the file, so differences in tabs, spaces and newlines do not show up when checking
differences between the optimized and non-optimized files. the differences between the optimized and non-optimized files.
\subsection{Execution} \subsection{Execution}
To execute the optimizer, the following command can be given:\\ To execute the optimizer, the following command can be given:\\
\texttt{./main <original file> <optimized file> <rewritten original file>} \texttt{./main.py <original file> <optimized file> <rewritten original file>}\\
There is also a script available that runs the optimizer and automatically
starts the program \emph{meld}. In meld it is easy to visually compare the
original file and the optimized file. The command to execute this script is:\\
\texttt{./run <benchmark name (e.g. whet)>}\\
\section{Testing} \section{Testing}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment