This is the mail archive of the
mailing list for the GCC project.
GPLv3 clarification - what constitutes IR
- From: laguest at mail dot com
- To: help at softwarefreedom dot org, gcc at gcc dot gnu dot org
- Cc: laguest at archeia dot com
- Date: Mon, 6 Mar 2017 18:12:31 +0100
- Subject: GPLv3 clarification - what constitutes IR
- Authentication-results: sourceware.org; auth=none
- Sensitivity: Normal
I'm looking into the possibility of adding a SPIR-V
(https://www.khronos.org/registry/spir-v) backend to GCC or as a
plug-in. The output of which would be binary from the compiler, not
binutils, with an option to extract a textual representation using an -f
flag. The positive of this would be that any language that GCC supports
could be used for GPGPU and graphics shading.
But would the GCC IR exception (mentioned in
https://www.gnu.org/licenses/gcc-exception-3.1-faq.html) cause any
SPIR-V output from GCC become GPLv3 licenced?
I have also posted this to the GCC ML for discussion as I don't think
it's clear whether or not something like SPIR-V would fall under Target
Code or IR.
Luke A. Guest.
P.S: I currently cannot post from my domain for some reason. I don't know why.