Contribute to OpenCilk
The OpenCilk project welcomes your expertise and enthusiasm.
Writing code
In addition to developing the OpenCilk codebase, we need your help extending existing code libraries to run in parallel with OpenCilk. Notable opportunities include x and y.
Writing blog posts and other documentation
Are you doing something with performance engineering that you want people to hear about? Are you writing how-tos or tutorials to help students with OpenCilk? We would love to hear! Have you prepared a presentation, video, or other educational material about OpenCilk? Let us know! If you’re unsure where to start or how your skills fit in, reach out!
Add to our list of resources
See resources.yaml
:
-
Agner Fog’s website and blog on software optimization resources external
-
Bit hack collection external bithacks : Collected by Sean Eron Anderson
-
Cilksan opencilk debugging parallel tool : OpenCilk race detector
-
rr + Cilksan opencilk debugging parallel tool : rr fork with Cilksan integration for navigating across race sites
-
Cilkscale debugging opencilk tool benchmarking profiling parallel : OpenCilk scalability analyzer and benchmarking tool
-
gperftools profiling tool cpu memory : C/C++ CPU and heap profilers
-
google-pprof profiling tool : gperftools profile visualization tool
-
Perf C2C profiling tool parallel : False sharing detection tool
-
Roblox outage traced back to performance engineering issues story external
-
Performance-engineering bracket pair colorization in VS Code story external
-
Intel oneAPI Threading Building Blocks external parallel-platform
-
cilk-mode (Emacs) ide goodies opencilk : Emacs minor mode for Cilk source code editing
Contact us on the mailing list (TBD) or with GitHub Issues.