Palmed: slight refactors
This commit is contained in:
parent
625f21739a
commit
8c3604fe73
2 changed files with 7 additions and 3 deletions
|
@ -200,3 +200,5 @@ set of \emph{flow sites} and \emph{jump sites}. The former is the set of
|
||||||
addresses just after a control flow instruction, while the latter is the set of
|
addresses just after a control flow instruction, while the latter is the set of
|
||||||
addresses to which jump instructions may jump. We then split the
|
addresses to which jump instructions may jump. We then split the
|
||||||
straight-line code of the symbol using the union of both sets as boundaries.
|
straight-line code of the symbol using the union of both sets as boundaries.
|
||||||
|
|
||||||
|
\todo{Add bb count}
|
||||||
|
|
|
@ -1,7 +1,9 @@
|
||||||
\section{Main contribution: evaluating \palmed{}}\label{sec:palmed_results}
|
\section{Evaluating \palmed{}}\label{sec:palmed_results}
|
||||||
|
|
||||||
The main contribution I made to \palmed{} is its evaluation harness and
|
Evaluating \palmed{} on the previously gathered basic blocks now requires, on
|
||||||
procedure. \todo{}
|
one hand, to define evaluation metrics and, on the other hand, an evaluation
|
||||||
|
harness to collect the throughput predictions from \palmed{} and the other
|
||||||
|
considered code analyzers, from which metrics will be derived.
|
||||||
|
|
||||||
\subsection{Evaluation harness}
|
\subsection{Evaluation harness}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue