The LLVM BuildingAJIT tutorial series teaches readers to build their own JIT class from scratch using LLVM’s ORC APIs, however the tutorial chapters have not kept pace with recent API improvements. Bring the existing tutorial chapters up to speed, write up a new chapter on lazy compilation (chapter code already available) or write a new chapter from scratch.
Expected results
Update chapter text for Chapters 1-3 – Easy, but offers a chance to get up-to-speed on the APIs.
Write chapter text for Chapter 4 – Chapter code is already available, but no chapter text exists yet.
Write a new chapter from scratch – E.g. How to write an out-of-process JIT, or how to directly manipulate the JIT’d instruction stream using the ObjectLinkingLayer::Plugin API.
Desirable skills:
Intermediate C++; Understanding of LLVM and the LLVM JIT in particular; Familiarity with RST (reStructed Text); Technical writing skills.
Hello. I have experience in writing security standards and regulations. I am pretty good at code. I would love to work on this project. Can we discuss details? (I would send my CV if needed)
@lhames@vvassilev
Hello. I was unable to send you a CV. The mail on your github hub is not correct or I do not perceive it correctly. Please send a valid one.
@lhames@vvassilev
Great . I have experience in writing regulations and security policies, documentation. I even compiled a threat model for a specific application (by code, etc.). What are my current actions? It’s still too early to send an offer if I understood correctly. I would probably start to describe something.
@lhames@vvassilev
Hello. It seems that there is already information about the organizations that Google accepted for the 22nd year. Do you have any information? And if you can check the mail (I sent information about the university)
Apologies for the delay. As I mentioned in our email exchange we needed some further clarifications from Google about the conflict in Ukraine. Google has a clarified that "GSoC 2022 is not accepting participants (Contributors, Mentors or Organization Administrators) from Russia, Belarus, or the so-called Donetsk People’s Republic (“DNR”) and Luhansk People’s Republic (“LNR”). " here.
If anything changes next year we would be happy to consider you as a GSoC candidate. In the meantime, you can always contribute to open source outside of the GSoC program.
Good morning, I’m interested in contributing. I previously followed the JIT tutorial by building my own version of it, but I noticed that some of the content were not up to date. I’m familiar with RST, and I’m familiar with c/c++. What do I need to do to provide some details to be able to contribute?
We don’t have a lot of time left. So I’d encourage you to reach out to us, sending your CV and a draft of your proposal.
The proposal should tell mentors that you know what, when and how to do, and you have the required skills to do it. I would recommend to pay extra attention to the proposal timeline and split it into weeks where you can describe the work and what would be the deliverable of the work. For example, Week N: We will implement X and Y and Chapter Z will be complete.
@vvassilev
I couldn’t send an email to llvm@discoursemail.com, so I sent you a message here with the proposal and the resume. Is that sufficient? Please let me know if I should go ahead and send the proposal through GSoC.
