https://github.com/weliveindetail/blog

Sporadic details on compilers, code and tooling from the world of LLVM
https://github.com/weliveindetail/blog

cpp jit lldb llvm native orc remote

Last synced: 10 days ago
JSON representation

Sporadic details on compilers, code and tooling from the world of LLVM

• Host: GitHub
• URL: https://github.com/weliveindetail/blog
• Owner: weliveindetail
• Created: 2016-06-07T19:21:26.000Z (over 8 years ago)
• Default Branch: main
• Last Pushed: 2024-08-29T15:41:04.000Z (3 months ago)
• Last Synced: 2024-10-31T09:36:49.710Z (17 days ago)
• Topics: cpp, jit, lldb, llvm, native, orc, remote
• Language: HTML
• Homepage: https://weliveindetail.github.io/blog/
• Size: 16.5 MB
• Stars: 4
• Watchers: 5
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# indetail dev blog

Sporadic details on compilers, code and tooling from the world of LLVM


https://weliveindetail.github.io/blog/

## Looking for help with a project that uses LLVM?

As a freelance developer I help small and mid-size companies to get up to speed with LLVM. Here in Berlin and remote.

I have a track record of remote work with various companies since 2016 and offer flexible conditions to match your demands. Feel free to reach out for questions via email or [schedule a video call](https://calendly.com/stefan-graenitz/30min) right away.

#### Build a solid foundation for your project

* Evaluate feasibility and estimate efforts early on.

* Set up build infrastructure for using LLVM, Clang or any other subject.

* Bring up a test suite to use the [LLVM integrated tester](https://llvm.org/docs/CommandGuide/lit.html) for your own project.

* Port your project to new platforms -- why not Windows?

#### Manage your own changes on LLVM

* Guidance on maintaining a fork downstream of LLVM.

* Get in touch with the community and communicate your issues.

* Represent your point of view and argue for your interests in the community.

#### Upstream your changes to LLVM

* Advice on [upstream guidelines](https://llvm.org/docs/SupportPolicy.html), risks and chances.

* Bring up solid tests for your use cases.

* Review your changes in [Phabricator](https://reviews.llvm.org/).

* Deal with [build bots](http://lab.llvm.org:8011/#/console) and test failures.

#### Workshops and trainings on-site or online

* LLVM upstream development best practices

* C++, library-based design and error handling in LLVM

---

Compiler development is the royal discipline of computing. It always demanded the highest skills from its makers and always fascinated me the most as a developer. Compilers are well understood in academics since long, but mainstream implementations were often lacking behind today's standards -- being quirky, proprietary and hard to master.

With the advent of [LLVM](https://stackoverflow.com/questions/2354725/what-exactly-is-llvm) a lot of this changed and today we have state of the art modular compiler technology right at our fingertips -- with a [clean three-phase architecture](www.aosabook.org/en/llvm.html), [open-source](https://github.com/llvm/llvm-project/) and reusable.

In my spare time I am hacking on compilers and tools and I use this blog to share my experiences. If that meets your own interests please join our [LLVM Social Berlin](https://www.meetup.com/de-DE/LLVM-Social-Berlin/), write an email or catch me on Twitter.