On 20/04/2021 16:15, Richard Kenner via Gcc wrote:
>> Just for the record, Google has no problem with the GPLv3. Google stopped
>> working on GCC because they made a company decision to use clang instead.
>> That decision was made for technical reasons, not licensing reasons.
>
> But note that some cellphone manufacturers (e.g, Samsung) have taken
> steps to prevent non-signed binaries from being loaded in their phones.
> This would have been problematic ("Tivoisation") if GPLv3 code was
> included in Android.
>
That would surely only be relevant if people wanted to use their
telephones to compile code? The license of the compiler does not matter
(except for libraries or code snippets that are copied directly by the
compiler to the binaries, and gcc has permissive license exceptions for
these.)
