summaryrefslogtreecommitdiffstats
path: root/eval.tex
diff options
context:
space:
mode:
Diffstat (limited to 'eval.tex')
-rw-r--r--eval.tex7
1 files changed, 3 insertions, 4 deletions
diff --git a/eval.tex b/eval.tex
index bf8dc5d..4b07961 100644
--- a/eval.tex
+++ b/eval.tex
@@ -40,17 +40,16 @@
Intel i++ & $\ge 1$\\
\bottomrule
\end{tabular}
- \caption{Unique bugs found in each tool.}
+ \caption{Unique bugs found in each tool. \JW{is `all versions' correct here? and should we add version numbers like in the Venn?}\YH{Yes it is actually correct here, I don't mind adding the specific version either though}}
\label{tab:unique_bugs}
\end{table}
We generate 6700 test-cases and provide them to three HLS tools: Vivado HLS, LegUp HLS and Intel i++.
We use the same test-cases across all tools for fair comparison.
We were able to test three different versions of Vivado HLS (v2018.3, v2019.1 and v2019.2).
-We were only able to test one version of LegUp: 4.0.
-At the point of writing, LegUp 7.5 is still GUI-based and therefore we could not script our tests.
+We tested one version of Intel i++ (version 18.1), and one version of LegUp (4.0).
+LegUp 7.5 is GUI-based and therefore we could not script our tests.
However, we were able to manually reproduce bugs found in LegUp 4.0 in LegUp 7.5.
-Finally, we tested one version of Intel i++ 18.1.
% Three different tools were tested, including three different versions of Vivado HLS. We were only able to test one version of LegUp HLS (version 4.0), because although LegUp 7.5 is available, it is GUI-based and not amenable to scripting. However, bugs we found in LegUp 4.0 were reproduced manually in LegUp 7.5.
% LegUp and Vivado HLS were run under Linux, while the Intel HLS Compiler was run under Windows.