Skip to content

Conversation

@hirooih
Copy link
Contributor

@hirooih hirooih commented Oct 17, 2021

This configuration demonstrates how to run the Embench on an FPGA board.

The current Embench distribution does not include any examples of a FPGA board configuration.
This is a result of my trial and error.

I hope this helps Embench users.

@jeremybennett
Copy link
Collaborator

@hirooih Nice work. I've again asked @PaoloS02 to review, but this is a good addition.

Do you have any results you can add to the embench-iot-results repository?

@hirooih
Copy link
Contributor Author

hirooih commented Oct 18, 2021

Thanks.

Do you have any results you can add to the embench-iot-results repository?

I can create a result in minutes.
But as I wrote in the README file, I made no performance tuning.
For example, the FPGA configuration fetch instruction from slow external NOR memory, and it has very small I cache size.
I use only -O2 -Os for compiler option.
I think it is not fair to send my result.
I hope Sifive guys will provide better configuration and its result.

"program": "${workspaceFolder}/bd/src/nbody/nbody",
// "args": [],
"cwd": "${workspaceRoot}",
// "environment": [],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these supposed to be removed?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean "args" and "environment"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. The two lines are useless for execution environments on FPGAs.

Instead, it's better to add the following line.

See Configuring C/C++ debugging for more configuration options.

Remove useless comments.
Add link to a link to VS code documentation.
@hirooih
Copy link
Contributor Author

hirooih commented Dec 5, 2021

@PaoloS02,
Thank you for reviewing this PR.
Is there any concerns in this PR?

BTW I have some updates to this PR.
Which is better for you, 1: open an separate PR or 2: add commits on this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants