blob: 1ffd4597be239baad36608b41271f37c40be8aba (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
+++
title = "Fuzz testing predictability of HLS tools"
author = "Yann Herklotz"
tags = []
categories = []
backlinks = ["1f4a"]
forwardlinks = ["1f4a"]
zettelid = "1f4b"
+++
One this note, one might be able to fuzz-test the predictability of HLS
tools. One simple property that one might want to show always hold is
the one noted in ([\#1f4a]). This could be done by adding dead-code to
hardware designs or input to HLS tools, and noting if the HLS tool ever
manage to optimise the hardware more due to these changes. This should
not happen if the HLS tools should be predictable, because that means
that adding random dead-code could actually lead to better designs, even
though the HLS should be designing that hardware in the first place.
[\#1f4a]: /zettel/1f4a
|
