From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Martin Jambor <mjambor@suse.cz>
Cc: Alexander Monakov <amonakov@ispras.ru>,
Thomas Schwinge <thomas@codesourcery.com>,
Cesar Philippidis <cesar@codesourcery.com>,
Chung-Lin Tang <chunglin_tang@mentor.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Allow building GCC with PTX offloading even without CUDA being installed (gcc and nvptx-tools patches)
Date: Mon, 16 Jan 2017 19:23:00 -0000 [thread overview]
Message-ID: <bcd092e2-a2c1-da80-5ec8-f0c370b62091@redhat.com> (raw)
In-Reply-To: <20170113182829.GB1867@tucnak>
On 01/13/2017 11:28 AM, Jakub Jelinek wrote:
> On Fri, Jan 13, 2017 at 06:19:02PM +0000, Joseph Myers wrote:
>>> --- libgomp/plugin/cuda/cuda.h.jj 2017-01-13 15:58:00.966544147 +0100
>>> +++ libgomp/plugin/cuda/cuda.h 2017-01-13 17:02:47.355817896 +0100
>>> @@ -0,0 +1,174 @@
>>> +/* CUDA API description.
>>> + Copyright (C) 2017 Free Software Foundation, Inc.
>>> +
>>> +This file is part of GCC.
>>> +
>>> +GCC is free software; you can redistribute it and/or modify
>>> +it under the terms of the GNU General Public License as published by
>>> +the Free Software Foundation; either version 3, or (at your option)
>>> +any later version.
>>> +
>>> +GCC is distributed in the hope that it will be useful,
>>> +but WITHOUT ANY WARRANTY; without even the implied warranty of
>>> +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>>> +GNU General Public License for more details.
>>> +
>>> +You should have received a copy of the GNU General Public License
>>> +along with GCC; see the file COPYING3. If not see
>>> +<http://www.gnu.org/licenses/>.
>>
>> The new file should presumably have the runtime license exception.
>
> Agreed (though, most likely the file isn't copyrightable anyway, but
> we use copyright boilerplate for various files that might not be
> copyrightable). But we should use it not just for cuda.h, but also
> for hsa.h and hsa_ext_finalize.h (CCing Martin who has added those).
>
> 2017-01-13 Jakub Jelinek <jakub@redhat.com>
>
> * plugin/cuda/cuda.h: Add GCC runtime library exception.
> * plugin/hsa.h: Likewise.
> * plugin/hsa_ext_finalize.h: Likewise.
Yea, seems like an oversight. Certainly the intention is that using
cuda & hsa in and of itself doesn't require the resulting executable to
be GPL licensed.
jeff
next prev parent reply other threads:[~2017-01-16 19:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 18:11 Jakub Jelinek
2017-01-13 18:19 ` Joseph Myers
2017-01-13 18:28 ` Jakub Jelinek
2017-01-16 19:23 ` Jeff Law [this message]
2017-01-18 20:27 ` Alexander Monakov
2017-01-18 22:18 ` Jakub Jelinek
2017-01-19 15:10 ` Alexander Monakov
2017-01-19 15:55 ` Jakub Jelinek
2017-01-21 15:28 ` Thomas Schwinge
2017-01-21 19:13 ` Jakub Jelinek
2017-05-03 9:08 ` Jakub Jelinek
2017-05-04 17:26 ` Thomas Schwinge
2022-04-06 12:39 ` Move 'libgomp/plugin/cuda/cuda.h' to 'include/cuda/cuda.h' (was: [PATCH] Allow building GCC with PTX offloading even without CUDA being installed (gcc and nvptx-tools patches)) Thomas Schwinge
2022-04-06 12:41 ` Jakub Jelinek
2022-04-07 22:27 ` libgomp nvptx plugin: Split 'PLUGIN_NVPTX_DYNAMIC' into 'PLUGIN_NVPTX_INCLUDE_SYSTEM_CUDA_H' and 'PLUGIN_NVPTX_LINK_LIBCUDA' " Thomas Schwinge
2022-04-08 7:35 ` Tom de Vries
2022-04-28 13:45 ` libgomp nvptx plugin: Split 'PLUGIN_NVPTX_DYNAMIC' into 'PLUGIN_NVPTX_INCLUDE_SYSTEM_CUDA_H' and 'PLUGIN_NVPTX_LINK_LIBCUDA' Thomas Schwinge
2022-05-05 19:18 ` [PING] " Thomas Schwinge
2022-05-12 11:57 ` [PING^2] " Thomas Schwinge
2022-05-12 12:09 ` Tom de Vries
2022-05-18 10:08 ` 'include/cuda/cuda.h': For C++, wrap in 'extern "C"' (was: [PATCH] Allow building GCC with PTX offloading even without CUDA being installed (gcc and nvptx-tools patches)) Thomas Schwinge
2022-05-18 10:11 ` 'include/cuda/cuda.h': Add parts necessary for nvptx-tools 'nvptx-run' " Thomas Schwinge
2024-03-07 11:53 ` GCN, nvptx: Fatal error for missing symbols in 'libhsa-runtime64.so.1', 'libcuda.so.1' " Thomas Schwinge
2024-03-07 11:55 ` Jakub Jelinek
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=bcd092e2-a2c1-da80-5ec8-f0c370b62091@redhat.com \
--to=law@redhat.com \
--cc=amonakov@ispras.ru \
--cc=cesar@codesourcery.com \
--cc=chunglin_tang@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=mjambor@suse.cz \
--cc=thomas@codesourcery.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).