public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: lkcl <luke.leighton@gmail.com>
Cc: GCC developers <gcc@gcc.gnu.org>
Subject: Re: rust non-free-compatible trademark
Date: Sun, 17 Jul 2022 19:41:01 +0200	[thread overview]
Message-ID: <20220717174101.GA4487@gnu.wildebeest.org> (raw)
In-Reply-To: <CAPweEDwrk9+10p_Ob7MmY9STQpgidXzbVchdL5Uefs4dFDGmdw@mail.gmail.com>

Hi Luke,

On Sun, Jul 17, 2022 at 06:06:45PM +0100, lkcl via Gcc wrote:
> given that gcc is *entirely implementing* the rust programming
> language (from scratch) and given that that implementation is not in
> fact implemented by the Rust Foundation (the Trademark Holders
> themselves) but by the gcc developers, then by definition *every*
> single line of source code constitutes "a patch", and according to
> the Trademark License they (the Rust Foundation) require that you
> seek explicit approval for its distribution.

I think you are misinterpreting when you need a trademark license for
usage a word mark in an implementation of a compiler for a programming
language. Note that gcc used to come with a full implementation of the
Java programming language, compiler, runtime and core library
implementation (for which I was the GNU maintainer). None of that
required a trademark license because the usage of the word java was
just for compatibility with the java programming language. And since
there was no claim of being or distributing Java(tm). The same is true
for Rust(tm) and the gccrs frontend.

Also note that the Rust Foundation is aware of the work and has
already integraeted parts of gcc through another alternative
implementation (based on libgccjit). As far as we know thy have no
problem with either alternative implementation of the Rust programming
language.

Cheers,

Mark

  reply	other threads:[~2022-07-17 17:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 15:28 lkcl
2022-07-17 16:25 ` Richard Biener
2022-07-17 16:47   ` lkcl
2022-07-17 18:24     ` Richard Kenner
2022-07-17 18:57   ` Alexandre Oliva
2022-07-17 16:31 ` Mark Wielaard
2022-07-17 17:06   ` lkcl
2022-07-17 17:41     ` Mark Wielaard [this message]
2022-07-17 18:11       ` lkcl
2022-07-17 18:29         ` lkcl
2022-07-17 22:59           ` Mark Wielaard
2022-07-17 23:07             ` lkcl
2022-07-17 23:55             ` Richard Kenner
2022-07-17 18:28       ` Richard Kenner
2022-07-17 18:54       ` Alexandre Oliva
2022-07-18  7:09   ` David Brown
2022-07-18  8:07     ` lkcl
2022-07-18  8:50       ` Jonathan Wakely
2022-07-18  9:06         ` lkcl
2022-07-18 14:30 ` lkcl
2022-07-18 17:11   ` Richard Kenner
2022-07-18 17:12   ` Richard Kenner
2022-07-18 18:32   ` Florian Weimer
2022-07-18 18:43     ` Arthur Cohen
2022-07-19  9:43       ` Florian Weimer
2022-07-18 19:35     ` lkcl
2022-07-18 21:01       ` David Malcolm
2022-07-18 23:09         ` lkcl
2022-07-19  9:27           ` Gabriel Ravier
2022-07-19 10:26             ` lkcl
2022-07-19 10:55               ` Jonathan Wakely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220717174101.GA4487@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=gcc@gcc.gnu.org \
    --cc=luke.leighton@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).