News for hackers. Stuff that matters.
Re:RISC-V on the Verge of Broad Adoption by sigjuice on Friday February 15, 2019 @02:13AM (#19169065)
How?
Re:RISC-V on the Verge of Broad Adoption by onli on Friday February 15, 2019 @05:58AM (#19169919)
You're right to ask, it does not. In the FOSS world the license of the compiler has nothing to do with the license of the compiled software, and that also goes for the GPL 3.

Probably some leftover thinking from proprietary products that tried to apply license restrictions on the compiled output.

Re:RISC-V on the Verge of Broad Adoption by pjmlp on Friday February 15, 2019 @08:21AM (#19170657)
Actually GCC has an explicit clause that GPL doesn't apply to the generated binary, otherwise you could not link to the C runtime library

"GCC Runtime Library Exception"

https://www.gnu.org/licenses/gcc-exception-3.1.en.html

This document was also the inspiration for the Classpath exception in OpenJDK.

Re:RISC-V on the Verge of Broad Adoption by pertymcpert on Friday February 15, 2019 @01:02PM (#19173113)
Right but that's because the compiler is emitting code into the binary that exists verbatim in the GCC source.
Re:RISC-V on the Verge of Broad Adoption by pjmlp on Friday February 15, 2019 @03:40PM (#19174510)
Which makes the assertion false, otherwise there wouldn't be a need for the "GCC Runtime Library Exception".

> "In the FOSS world the license of the compiler has nothing to do with the license of the compiled software".

Re:RISC-V on the Verge of Broad Adoption by onli on Saturday February 16, 2019 @05:22AM (#19178034)
There is no other FOSS compiler that influences the license of the compiled software, afaik. So I think that statement holds up anyway.