avast / avast/llvm

Document the modifications to llvm and maybe upstream them

Open
#5 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
LLVM
Stars
19
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Relying on a custom version of LLVM prevents proper packaging. It is inconvenient to have multiple versions of llvm on a machine. And it is especially inconvenient to build a custom llvm, since building of it takes long. I wonder if your patches can be upstreamed and built and shipped as a part of vanilla llvm, and if there are patches that cannot be upstreamed, if they can be put into a separate lib. Of course, a prereq for that is to port them all to the latest llvm (currently 12, but the differences (in API) from 11 are pretty small).

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by inventorying the custom LLVM patches and comparing them with LLVM 12 APIs; done means documenting the modifications, identifying which patches can be upstreamed, and separating any remaining non-upstreamable work.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.