Believing in numbers and fair evaluation, I've compared RAP and LLVM-CFI. RAP is faster, LLVM-CFI is more precise. RAP is incredibly hard to use and its future is uncertain while LLVM-CFI is just a command line argument away. Details at nebelwelt.net/blog/20181226-… Comments welcome 🤗
18
28
79
- you too are violating GPLv2 section 3 with your release, please fix it. not to mention that it's quite silly to distribute a binary gcc plugin since it will only work with the exact same gcc version you used to build it for. [11/n]
1
Link to source code is included via the blog post so I should be fine
1
1
Replying to @gannimo
no, it's not fine. read GPLv2 section 3 for the possible options.

Dec 27, 2018 · 1:13 PM UTC

2
1
Replying to @paxteam @gannimo
i think you had enough time to fix the GPL violation in your repo. if you don't remedy it now, you'll leave me no choice but to ask github to take it down. this is your last warning.
1
1
Replying to @paxteam @gannimo
My guess would be that provision 3a is met if the kernel tarball is present in the binary's directory as it requires the binary to be accompanied by the complete source code. Right now it's only the patch. Is this the missing thing you're referring to?
1