oasisprotocol / oasisprotocol/oasis-core
SGX profiling
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
https://software.intel.com/en-us/get-started-with-vtune
https://software.intel.com/en-us/node/708952
https://software.intel.com/en-us/blogs/2016/01/07/intel-sgx-debug-production-prelease-whats-the-difference
Make sure VTune/IntelSGXSDK versions are compatible
Apparently this can lead to issues.
Also keep in mind variable length printf may not work
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files or tests. Start by reviewing the three linked Intel VTune and SGX resources, then determine how VTune and Intel SGX SDK version compatibility and variable-length printf limitations should be documented; done means those constraints are clearly captured.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100