Review of Guideline #35

Review of Guideline #35

Formatting

Item	Outcome
Guideline complies with the Guideline-Template	Yes
Name of guideline responsible with affiliation is clearly stated	Yes

Is the audience of the guideline correctly specified?

Yes

Is the expertise required to write the guideline correctly specified?

Yes

Are the keywords well selected?

Change to Code optimisation, GPU, CPU, FPGA

Are parts of the guideline too generic or too specific?

No. Its good.

Does the guideline explicitly refer to the handbook? To which part of the deliverable is it relevant (e.g., chapter of D1.2/D1.3)?

No

Does the guideline specify the work done in the project that can benefit from the guideline?

Yes

Other comments

1. Guideline advice:

2. Insights that led to the guideline:

3. Recommended implementation method of the guideline along with a solid motivation for the recommendation: Recomendation is good. However, I am not sure whether HLS allows C++ code at all. Just check on that and if necessary adjust.

Some small typos:

• ride --> ride

4. Instantiation of the recommended implementation method in the reference platform:

5. Evaluation of the guideline in reference applications:

6. References:

Track changes:

1. 02/08/2018: Guideline created
2. 14/12/2018: guideline reviewed.
3. 30/01/2019: guideline updated