diff options
author | Yann Herklotz <ymh15@ic.ac.uk> | 2020-09-14 15:05:15 +0000 |
---|---|---|
committer | overleaf <overleaf@localhost> | 2020-09-14 15:47:05 +0000 |
commit | f09e782d0925bc735aadc29bf595d1e3cc187351 (patch) | |
tree | 9c323f14437787f81274f7aba10be2289f5acc94 /main.tex | |
parent | 11f9b46c8c5b3152435b3e5de43008e558f980dc (diff) | |
download | fccm21_esrhls-f09e782d0925bc735aadc29bf595d1e3cc187351.tar.gz fccm21_esrhls-f09e782d0925bc735aadc29bf595d1e3cc187351.zip |
Update on Overleaf.
Diffstat (limited to 'main.tex')
-rw-r--r-- | main.tex | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -115,7 +115,7 @@ High-level synthesis (HLS) is becoming an increasingly important part of the computing landscape, even in safety-critical domains where correctness is key. As such, HLS tools are increasingly relied upon. In this paper, we investigate whether they are trustworthy. -We have subjected three widely used HLS tools -- LegUp, Xilinx Vivado HLS, and the Intel HLS Compiler -- to a rigorous fuzzing campaign using thousands of random, valid C programs that we generated using a modified version of the Csmith tool. For each C program, we compiled it to a hardware design using the HLS tool under test and checked whether that hardware design generates the same output as an executable generated by the gcc compiler. When discrepancies arose between gcc and the HLS tool under test, we reduced the C program to a minimal example in order to zero in on the potential bug. Our testing campaign has revealed that all three HLS tools can be made either to crash or to generate wrong code when given valid C programs, and thereby underlines the need for these increasingly trusted tools to be more rigorously engineered. +We have subjected three widely used HLS tools -- LegUp, Xilinx Vivado HLS, and the Intel HLS Compiler -- to a rigorous fuzzing campaign using thousands of random, valid C programs that we generated using a modified version of the Csmith tool. For each C program, we compiled it to a hardware design using the HLS tool under test and checked whether that hardware design generates the same output as an executable generated by the gcc \JW{We should decide on a consistent way to capitalise `gcc'. I vote for `GCC' because that's how Wikipedia writes it.} compiler. When discrepancies arose between gcc and the HLS tool under test, we reduced the C program to a minimal example in order to zero in on the potential bug. Our testing campaign has revealed that all three HLS tools can be made either to crash or to generate wrong code when given valid C programs, and thereby underlines the need for these increasingly trusted tools to be more rigorously engineered. \end{abstract} %% |