blob: 45fcc27ca03368ce8837b5070978d5c42d207b41 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
\section{Evaluation}
\NR{Do we want to collect C-to-Verilog compile time?}
\begin{table}
\begin{tabular}{lcccccc}
\toprule
Benchmark & Cycles & Frequency & LUTs & Registers & BRAMs\\
\midrule
adpcm & 30241 &90.05 & 7719 & 12034 & 7\\
aes & 8489 & 87.83 & 24413 & 23796 & 19 \\
gsm & 7190 & 119.25 & 6638 & 9201 & 3 \\
mips & 7754 & 98.95 & 5049 & 4185 & 0 \\
\bottomrule
\end{tabular}
\caption{CHstone programs synthesised in LegUp 5.1}
\end{table}
\begin{table}
\begin{tabular}{lcccccc}
\toprule
Benchmark & Cycles & Frequency & LUTs & Registers & BRAMs\\
\midrule
adpcm & XXX & XXX & XXX & XXX & XXX \\
aes & 41958 & & & & \\
gsm & 21994 & & & & \\
mips & 18482 & 78.43 & 10617 & 7690 & 0 \\
\bottomrule
\end{tabular}
\caption{CHstone programs synthesised in CoqUp}
\end{table}
The difference in cycle counts shows the degree of parallelism that LegUp's scheduling and memory system can offer. However, their Verilog generation is not guaranteed to be correct. Although the runtime LegUp outputs are tested to be correct for these programs, this does not provide any confidence on the correctness of Verilog generation of any other programs. Our Coq proof mechanisation guarantees that generated Verilog is correct for any input program that uses the subset of CompCert instructions that we have proven to be correct.
%%% Local Variables:
%%% mode: latex
%%% TeX-master: "main"
%%% End:
|
