<oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
  <dc:contributor>Pozzi, Laura</dc:contributor>
  <dc:creator>Ferretti, Lorenzo</dc:creator>
  <dc:date>2020-10-30</dc:date>
  <dc:description xmlns:ns0="xml" ns0:lang="en">High Level Synthesis (HLS) is a process which, starting from a high-level description of an application (C/C++), generates the  corresponding RTL code describing the hardware implementation of the desired functionality. The HLS process is usually  controlled by user-given directives (e.g., directives to set whether or not to unroll a loop) which influence the resulting  implementation area and latency. By using HLS, designers are able to rapidly generate different hardware implementations of  the same application, without the burden of directly specifying the low level implementation in detail. Nonetheless, the  correlation among directives and resulting performance is often difficult to foresee and to quantify, and the high number of  available direct- ives leads to an exponential explosion in the number of possible configurations. In addition, sampling the  design space involves a time-consuming hardware synthesis, making a brute-force exploration infeasible beyond very simple  cases. However, for a given application, only few directive settings result in Pareto- optimal solutions (with respect to metrics  such as area, run-time and power), while most are dominated. The design space exploration problem aims at identifying close  to Pareto-optimal implementations while synthesising only a small portion of the possible configurations from the design space.  In this dissertation I present an overview of the HLS design flow, followed by a discussion about existing strategies in literature.  Moreover, I present new exploration methodologies able to automatically generate optimised implementations of hardware  accelerators. The proposed approaches are able to retrieve a close approximation of the real Pareto solutions while  synthesising only a small fraction of the possible design, either by smartly navigating their design space or by leveraging prior  knowledge. Herein, I also present a database of design space explorations whose goal is to help researchers to design new  strategies by offering a reliable source of knowledge for machine learning based approaches, and standardise the  methodologies evaluation. Lastly, the stepping-stones of a new approach relying on deep learning strategies with graph neural  networks is presented, and final remarks about future research directions are discussed.</dc:description>
  <dc:format>application/pdf</dc:format>
  <dc:identifier>https://susi.usi.ch/global/documents/319184</dc:identifier>
  <dc:identifier>https://n2t.net/ark:/12658/srd1319184</dc:identifier>
  <dc:identifier>https://susi.usi.ch/documents/319184/files/2020INFO016.pdf</dc:identifier>
  <dc:language>eng</dc:language>
  <dc:relation>info:eu-repo/semantics/altIdentifier/urn/urn:nbn:ch:rero-006-118902</dc:relation>
  <dc:relation>info:eu-repo/semantics/altIdentifier/ark/12658/srd1319184</dc:relation>
  <dc:rights>info:eu-repo/semantics/openAccess</dc:rights>
  <dc:rights>License undefined</dc:rights>
  <dc:subject xmlns:ns1="xml" ns1:lang="en">Design space exploration</dc:subject>
  <dc:subject xmlns:ns2="xml" ns2:lang="en">High-level synthesis</dc:subject>
  <dc:subject xmlns:ns3="xml" ns3:lang="en">HW/SW co-design</dc:subject>
  <dc:subject xmlns:ns4="xml" ns4:lang="en">Hardware accelerators</dc:subject>
  <dc:subject xmlns:ns5="xml" ns5:lang="en">Heterogeneous architectures</dc:subject>
  <dc:subject xmlns:ns6="xml" ns6:lang="en">Computer architectures</dc:subject>
  <dc:subject>info:eu-repo/classification/udc/004</dc:subject>
  <dc:title xmlns:ns7="xml" ns7:lang="en">Design space exploration in high-level synthesis</dc:title>
  <dc:type>http://purl.org/coar/resource_type/c_db06</dc:type>
</oai_dc:dc>
