diff options
| author | Yann Herklotz <git@yannherklotz.com> | 2021-04-14 00:03:47 +0100 |
|---|---|---|
| committer | Yann Herklotz <git@yannherklotz.com> | 2021-04-14 00:03:47 +0100 |
| commit | 2e70aee3a563ca6c78c75be1922c9f657a3fc40a (patch) | |
| tree | c2972b4c15b218090df602275635369d2dd61e30 /algorithm.tex | |
| parent | b9891db033123ed317a3eb71a1e75930a933378a (diff) | |
| download | oopsla21_fvhls-2e70aee3a563ca6c78c75be1922c9f657a3fc40a.tar.gz oopsla21_fvhls-2e70aee3a563ca6c78c75be1922c9f657a3fc40a.zip | |
Some small fixes
Diffstat (limited to 'algorithm.tex')
| -rw-r--r-- | algorithm.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/algorithm.tex b/algorithm.tex index 944c1b3..deafece 100644 --- a/algorithm.tex +++ b/algorithm.tex @@ -9,8 +9,8 @@ The availability of \compcert{}~\cite{leroy09_formal_verif_realis_compil} also p %Since a lot of existing code for HLS is written in C, supporting C as an input language, rather than a custom domain-specific language, means that \vericert{} is more practical. %An alternative was to support LLVM IR as an input language, however, to get a full work flow from a higher level language to hardware, a front end for that language to LLVM IR would also have to be verified. \JW{Maybe save LLVM for the `Choice of implementation language'?} We considered Bluespec~\cite{nikhil04_blues_system_veril}, but decided that although it ``can be classed as a high-level language''~\cite{greaves_note}, it is too hardware-oriented to be suitable for traditional HLS. -We also considered using a language with built-in parallel constructs that map well to parallel hardware, such as occam~\cite{page91_compil_occam}, Spatial~\cite{spatial} or Scala~\cite{chisel}, \JWcouldcut{but found these languages too niche.} -% However, this would not qualify as being HLS due to the manual parallelism that would have to be performed. \JW{I don't think the presence of parallelism stops it being proper HLS.} +We also considered using a language with built-in parallel constructs that map well to parallel hardware, such as occam~\cite{page91_compil_occam}, Spatial~\cite{spatial} or Scala~\cite{chisel}. +% However, this would not qualify as being HLS due to the manual parallelism that would have to be performed. \JW{I don't think the presence of parallelism stops it being proper HLS.} %\JP{I think I agree with Yann here, but it could be worded better. At any rate not many people have experience writing what is essentially syntactic sugar over a process calculus.} %\JW{I mean: there are plenty of software languages that involve parallel constructs. Anyway, perhaps we can just dismiss occam for being too obscure.} |