diff options
| -rw-r--r-- | eval_rewrite.tex | 3 | ||||
| -rw-r--r-- | method-new.tex | 5 |
2 files changed, 3 insertions, 5 deletions
diff --git a/eval_rewrite.tex b/eval_rewrite.tex index d81b158..e084b05 100644 --- a/eval_rewrite.tex +++ b/eval_rewrite.tex @@ -44,7 +44,8 @@ \label{tab:unique_bugs} \end{table} -To evaluate the different HLS tools 10,000 \JW{check numbers} test cases were generated and fed into each tool, keeping the test cases constant so that the comparison between the tools was fair. Three different tools were tested, including three different versions of Vivado, which are shown in Table~\ref{tab:unique_bugs}. Bugs were found in all tools that were tested, and in total, ?? unique bugs were found and reported to the tool vendors. +To evaluate the different HLS tools 10,000 \JW{check numbers} test cases were generated and fed into each tool, keeping the test cases constant so that the comparison between the tools was fair. Three different tools were tested, including three different versions of Vivado HLS, which are shown in Table~\ref{tab:unique_bugs}. Bugs were found in all tools that were tested, and in total, \ref{??} unique bugs were found and reported to the tool vendors. +We were only able to test one version of LegUp HLS (version 4.0). LegUp 7.5 is GUI-based and not suitable for scripting; however, bugs we found in LegUp 4.0 were reproduced manually in LegUp 7.5. \subsection{Bugs found} diff --git a/method-new.tex b/method-new.tex index e931f70..8ff8281 100644 --- a/method-new.tex +++ b/method-new.tex @@ -172,10 +172,7 @@ We do not count time-outs as bugs, but we record them. %\paragraph{Tool-specific trivia} %Vivado HLS implements C and RTL simulation by default. -\JW{Maybe move this later on? -``We were only able to test one version of LegUp HLS (version 4.0). -LegUp 7.5 is GUI-based and not suitable for scripting; however, bugs we found in LegUp 4.0 were reproduced manually in LegUp 7.5.'' -} + %For all tools, we set a 5-minute and 2-hour for C simulation and RTL simulation respectively. %In cases where simulation takes longer, we do not consider them as failures or crashes and we record them. % When testing Intel HLS, we place three time-outs since its execution is generally slower than other HLS tools: a \ref{XX}-minute time-out for C compilation, a \ref{XX}-hour time out for HLS compilation and a \ref{XX}-hour time-out for co-simulation. |