From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 102682 invoked by alias); 6 Mar 2017 17:39:57 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 102666 invoked by uid 89); 6 Mar 2017 17:39:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=HTo:D*mail.com, H*f:sk:trinity, HX-Envelope-From:sk:richard, Taylor X-HELO: mail-wm0-f68.google.com Received: from mail-wm0-f68.google.com (HELO mail-wm0-f68.google.com) (74.125.82.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 06 Mar 2017 17:39:55 +0000 Received: by mail-wm0-f68.google.com with SMTP id n11so14954329wma.0 for ; Mon, 06 Mar 2017 09:39:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=okoPSY7rXjTjQN03oRbXMY5azQWjfN6yntFBjozXFrw=; b=aoSVgGQCfiUA0DSJXC0HjAawHFjsVRDWMApt0tnok4Khh/3VkC9gtFABWLuC7Rwvx0 6W2nDi66Ak5M0PhYF55Xhds5X3bG7O1ehiL02yKmF5kfHN78jBL0uboYrAIpH/x+qStE Jabrw7Dcd97hjpCuu+lQ++tph2GP/qKwFG1I5uCjT7FYVxmFyO4bon2+hk5ZNzhdx9fb 9UGK84ET1Kx6V+tp+gM7Zo1aYuaJbPDqsBqMMT2s+/uMxOrW+o0SQ2TXpFOufigcwPRc CMUnZ3tS2QuPyzSnNVXKFJ+9aZ2AV7Reoc2LMCzZJjqv2KqtRW2vFFlkroRNFn19XphS ZrAw== X-Gm-Message-State: AMke39n+9w+TrmcmQEDR8ayPUbMFXYl0Gp9KKVetGLN6PZ3Zc+9lUSsKths2QpNE5RU7Rg== X-Received: by 10.28.138.136 with SMTP id m130mr14462285wmd.72.1488821993813; Mon, 06 Mar 2017 09:39:53 -0800 (PST) Received: from android-4c5a376a18c0e957.fritz.box (p5DCECD8C.dip0.t-ipconnect.de. [93.206.205.140]) by smtp.gmail.com with ESMTPSA id b10sm15674752wmi.34.2017.03.06.09.39.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2017 09:39:53 -0800 (PST) Date: Mon, 06 Mar 2017 17:39:00 -0000 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: GPLv3 clarification - what constitutes IR To: Ian Lance Taylor ,Ian Lance Taylor via gcc ,laguest@mail.com CC: help@softwarefreedom.org,GCC Development ,laguest@archeia.com From: Richard Biener Message-ID: <755C98CF-0062-48E4-B575-862481D60CB3@gmail.com> X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00008.txt.bz2 On March 6, 2017 6:29:49 PM GMT+01:00, Ian Lance Taylor via gcc wrote: >On Mon, Mar 6, 2017 at 9:12 AM, wrote: >> >> 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. > >I am not a lawyer and this is not legal advice. > >Generating SPIR-V output would not cause that output to become GPLv3 >licensed. However, linking the result against the GCC support >libraries, as is normally required for any program generated by GCC, >and then distributing the resulting executable to other people, would >require you to use an eligible compilation process (as defined by the >GCC Runtime Library Exception license that you cite). What this means >in practice is that you can not take SPIR-V, do further processing it >using a proprietary compiler, link the result with the GCC runtime >libraries, and then distribute the resulting program to anybody else. > >I don't think it is necessary to determine whether SPIR-V is "target >code" or "intermediate representation" to draw that conclusion. Note we already have the HSAIL and PTX backends which have the very same (n= on-)problem. Both invoke a proprietary compiler for final compilation. Richard. >Ian