diff options
| author | n.ramanathan14 <n.ramanathan14@imperial.ac.uk> | 2020-09-14 18:51:38 +0000 |
|---|---|---|
| committer | overleaf <overleaf@localhost> | 2020-09-14 19:09:32 +0000 |
| commit | 0cd734816ad8fc58933ecc1c6a79a36903d36158 (patch) | |
| tree | f2a45e714cdbf56d78fed9323c55cd6e61dc4fd0 | |
| parent | b7d1d32bdb1098091498439ec2f75c78dbe0d582 (diff) | |
| download | fccm21_esrhls-0cd734816ad8fc58933ecc1c6a79a36903d36158.tar.gz fccm21_esrhls-0cd734816ad8fc58933ecc1c6a79a36903d36158.zip | |
Update on Overleaf.
| -rw-r--r-- | method-new.tex | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/method-new.tex b/method-new.tex index 695a173..1e81163 100644 --- a/method-new.tex +++ b/method-new.tex @@ -20,13 +20,13 @@ This section describes how we conducted our testing campaign, the overall flow o \subsection{Generating programs via CSmith} \label{sec:method:csmith} -\NR{ -Questions: -\begin{itemize} - \item Do we use Csmith's hashing or our own hashing now? Is that what \texttt{transparent\_crc} is for? -\end{itemize} -} -\YH{I believe that we are now maybe using our own hashing, even though one of the bugs in Vivado was found in the Csmith hashing algorithm.. So I don't know how best to mention that.} +% \NR{ +% Questions: +% \begin{itemize} +% \item Do we use Csmith's hashing or our own hashing now? Is that what \texttt{transparent\_crc} is for? +% \end{itemize} +% } +% \YH{I believe that we are now maybe using our own hashing, even though one of the bugs in Vivado was found in the Csmith hashing algorithm.. So I don't know how best to mention that.} For our testing campaign, we require a random program generator that produces C programs that are both semantically valid and feature-diverse; Csmith~\cite{yang11_findin_under_bugs_c_compil} meets both these criteria. %Csmith is randomised code generator of C programs for compiler testing, that has found more than 400 bugs in software compilers. |