None. It is a feature by feature (partially implemented) rip off, even acknowledged.
-
They do NOT do that, they wrote a simple plugin, which has to be GPLv3 because it DIRECTLY links into and calls GPLv3'd GCC.
Nevermind the fact that there are many Linux arch ports that DO link libgcc, so they're wrong (or lying) about that too.
-
-
The whole thing is an incorrect (either by negligence or malice) wank to try to attempt to restrict usage of RAP outside the kernel.
-
It's basically trying to abuse the FSF's "no proprietary GCC plugins" rules but it gets it completely wrong.
End of conversation
New conversation -
-
-
"config PAX_RAP depends on X86_64 && GCC_PLUGINS" your point being?
-
there are other grsec gcc plugins with the same attempted license hack
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.