Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Java DaCapo benchmark sample provide fixes #646
base: oe_port
Are you sure you want to change the base?
Add Java DaCapo benchmark sample provide fixes #646
Changes from 12 commits
28ece2d
2c6ee45
adb6119
1d3b408
6b4ce95
f5f5d04
7368de3
d5d745e
fbaa03c
18d3f1c
dbb7ed9
30d52f4
30a553e
c6af984
7518776
a65be49
09b5a1f
1c9e089
9dd5458
fdb1381
4a2993a
066e154
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just
host-config.json
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like making them specific to the application, so from looking at the filename, you have a better understanding what's inside.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find that weird and I don't think we should advocate/recommend that. A folder should be the logical unit that groups things and inside that we have a standard layout. Don't you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I would say that there are two options:
We assume that the enclave/host configs should have well-known fixed filenames, i.e.
enclave_config.json
andhost_config.json
. This would be similar to theDockerfile
orMakefile
convention. In that case though, the--encave-config
and--host-config
parameters should be optional and only needed if a user (for whatever reason) wants to override the filenames. This would be similar to howdocker
ormake
work -- otherwise we are forcing users to provide redundant options with each invocation.We don't assume that there is a single approved filename and instead require users to be explicit (as it is now).
As you can tell, I'm in favour of (2), as I'm not a big fan of "magic" filenames that people must remember. That said, if people prefer (1), I'm also ok with that.