diff options
| author | n.ramanathan14 <n.ramanathan14@imperial.ac.uk> | 2020-09-12 11:28:01 +0000 |
|---|---|---|
| committer | overleaf <overleaf@localhost> | 2020-09-12 12:37:26 +0000 |
| commit | 6a29bd0d8c8cb7a6aeeba607489705b5afa528d8 (patch) | |
| tree | 6356185477b6ae796fce45e3a7072ce9e2f0ff32 /intro.tex | |
| parent | dd4f46e46cd7fcfb93c7212cb3ff5cc424b38b54 (diff) | |
| download | fccm21_esrhls-6a29bd0d8c8cb7a6aeeba607489705b5afa528d8.tar.gz fccm21_esrhls-6a29bd0d8c8cb7a6aeeba607489705b5afa528d8.zip | |
Update on Overleaf.
Diffstat (limited to 'intro.tex')
| -rw-r--r-- | intro.tex | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -43,9 +43,11 @@ Thus, it was natural to adopt program fuzzing for our HLS testing campaign. % \NR{Yann, please double check my claims about the bug. I hope I accurately described what we discussed. }\YH{Yes I agree with all that, I think that is a good description of it} \end{framed} +\paragraph{Our contribution} + We have tested three widely used HLS tools: LegUp~\cite{canis13_legup}, Xilinx Vivado HLS~\cite{xilinx20_vivad_high_synth}, and the Intel HLS Compiler~\cite{?}. For all three tools, we were able to find valid C programs that cause crashes while compiling and valid C programs that cause wrong RTL to be generated. We have submitted a total of \ref{?} bug reports to the developers, \ref{?} of which have been confirmed and \ref{?} of which have now been fixed at the time of writing. -\paragraph{Our contribution} + \begin{itemize} \item Fuzzing flow \item Tested against three tools |