diff options
| -rw-r--r-- | intro.tex | 4 | ||||
| -rw-r--r-- | main.tex | 4 | ||||
| -rw-r--r-- | method-new.tex | 2 | ||||
| -rw-r--r-- | tool-figure.tex | 4 |
4 files changed, 8 insertions, 6 deletions
@@ -16,7 +16,9 @@ Furthermore, fuzzing tools can be configured by users to generate and avoid part % % Our method is brought over from the compiler testing literature. % Program fuzzing is bla.. -% Fuzzing enables us to overcome +% Fuzzing enables us to overcome + +Fuzzing is an effective random testing technique whereby random inputs are provided to the software under test and the output is checked for correctness. @@ -159,14 +159,14 @@ We have subjected three widely used HLS tools -- LegUp, Xilinx Vivado HLS, and t \input{intro} +\input{related} + \input{method-new} % \input{testing-system-new} \input{eval_rewrite} -\input{related} - \input{conclusion} %\begin{acks} diff --git a/method-new.tex b/method-new.tex index 0035f8a..bb07ae6 100644 --- a/method-new.tex +++ b/method-new.tex @@ -94,7 +94,7 @@ We disable generation of unions and unions within C structures as these weren't Several tool-specific restrictions are also put in place. We enforce the the main function of these programs must not have any input arguments, to allow effective HLS synthesis and simulation. -We disable structure packing within Csmith since it generates the \code{``\#pragma pack(1)''} before structure definition. +We disable structure packing within Csmith since it generates the ``\code{\#pragma pack(1)}'' before structure definition. This pragma cause conflicts in HLS tools since it is interpreted as an unsupported pragma. We also disable generation of bit-wise binary AND and OR operations. When we applied these bit-wise operators applied on constants caused specific versions of Vivado HLS to error out as ``Wrong pragma usage''. diff --git a/tool-figure.tex b/tool-figure.tex index de4961f..fe38dd3 100644 --- a/tool-figure.tex +++ b/tool-figure.tex @@ -26,7 +26,7 @@ block/.style={draw, minimum width=20mm, minimum height=8mm,align=center}, \end{tikzpicture} % \includegraphics{} \caption{A figure that shows the overall flow. - \NR{Is that more accurate now? Do programs that crash get reduced? Do pragmas get reduced too?} + \NR{Is that more accurate now? Do programs that crash get reduced? Do pragmas get reduced too?}\YH{Yes that is accurate, crashes and failures are reduced now.} } \label{fig:method:toolflow} -\end{figure*}
\ No newline at end of file +\end{figure*} |