cameron314 / cameron314/readerwriterqueue
Help with profiling OSX M1
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.6k
- Forks
- 736
- Avg merge
- 10d 5h
- Merged PRs (30d)
- 1
Description
Hi!
I saw
Note that it's only been tested on x86(-64); if someone has access to other processors I'd love to run some tests on anything that's not x86-based.
In the readme.
I have a mac m1 (arm) processor. If there is a suite of tests I can run for you I'd be thrilled to help.
Let me know
Contributor guide
No contributing guide indexed for this repository
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
Start with the README's note that testing has only covered x86(-64), then inspect the repository for any existing test or profiling entry points. Run the available checks on an OSX M1 system and report the results, including any ARM-specific failures or missing coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100