public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Simon Wright <simon@pushface.org>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: zlynx@acm.org, gcc@gcc.gnu.org
Subject: Re: License compliance on updating gcc runtime libraries
Date: Wed, 27 Feb 2019 19:26:00 -0000	[thread overview]
Message-ID: <1A1950D7-2119-466A-96E7-99C541CD5B70@pushface.org> (raw)
In-Reply-To: <20190227183725.D694833CAC@vlsi1.gnat.com>

On 27 Feb 2019, at 18:37, Richard Kenner <kenner@vlsi1.ultra.nyu.edu> wrote:
> 
> 1) Whether executing a program is considered making a copy under
> copyright law.

I had a look through some of the published judgements, and it's clear that in the US at least copying into RAM (for whatever purpose, and provided the copy has more than fleeting duration) counts as copying for copyright purposes.

I can't help feeling (however useless feelings are in the face of the 9th Circuit) that a software publisher should be able to rely on other methods to retain control of their proprietary software. After all, ARM-based MCUs are capable of executing code directly from Flash, with no copying at all.

  reply	other threads:[~2019-02-27 19:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27  9:06 hiraku.toyooka
2019-02-27  9:32 ` Jonathan Wakely
2019-02-28 10:28   ` hiraku.toyooka
2019-02-27 12:41 ` Richard Kenner
2019-02-27 13:13   ` Simon Wright
2019-02-27 13:20     ` Richard Kenner
2019-02-27 14:22       ` Zan Lynx
2019-02-27 18:37         ` Richard Kenner
2019-02-27 19:26           ` Simon Wright [this message]
2019-02-28 10:33   ` hiraku.toyooka

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=1A1950D7-2119-466A-96E7-99C541CD5B70@pushface.org \
    --to=simon@pushface.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=zlynx@acm.org \
    /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).