From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] pocl
Date: Wed, 3 Jan 2024 05:26:43 -0700 [thread overview]
Message-ID: <19a0d8be-a17e-438f-bf3b-71ddd7cafee9@SystematicSW.ab.ca> (raw)
In-Reply-To: <20240103210007.548250af5b62f082bc441d8c@nifty.ne.jp>
On 2024-01-03 05:00, Takashi Yano via Cygwin-apps wrote:
> On Wed, 3 Jan 2024 04:38:02 -0700
> Brian Inglis wrote:
>> On 2024-01-03 02:29, Takashi Yano via Cygwin-apps wrote:
>>> On Wed, 3 Jan 2024 08:54:17 +0100
>>> Marco Atzeri wrote:
>>>> On 03/01/2024 06:25, Takashi Yano via Cygwin-apps wrote:
>>>>> On Wed, 3 Jan 2024 14:14:12 +0900
>>>>> Takashi Yano via Cygwin-apps <cygwin-apps@cygwin.com> wrote:
>>>>>> I'd like to adopt the pocl package.
>>>>>> - Update to latest upstream release.
>>
>>>> $ git diff |grep "^+"
>>>> +++ b/cygwin-pkg-maint
>>>> +pocl Takashi Yano
>>
>>>>> Sorry, the latest upstream release is 5.0 however, 4.0 and later
>>>>> cannot be built in current cygwin because LLVM package is old.
>>>>> This update is up to 3.1.
>>
>>>>>> - Enable CUDA support.
>>
>>>> Curiosity, how do we support CUDA on Cygwin ?
>>
>>> nvidia cuda toolkit is used in build stage of user programs.
>>> Although this is not very desirable for cygwin package, I thought
>>> that the advantage of being able to use the GPU was greater than
>>> the disadvantage.
>>> However, on the second thought, cuda support should be a separeted
>>> package from the base package, and suggest installing cuda toolkit
>>> in the install stage of of that package.
>>> Let me consider a bit. If you have any idea, please let me know.
>>
>> Please note CUDA is Nvidia proprietary closed source - I do not think we can or
>> should touch it when OpenCL 3+ supports Nvidia devices.
>> Fedora does not support CUDA although others do in their non-free "sources".
>
> We do not touch CUDA itself or distribute its binaries, but just use binaries
> distributed by NVIDIA. Source code in pocl is not NVIDIA proprietary. In that
> sense, cygwin itself uses microsoft proprietary closed source modules.
Cygwin provides and runs open source tools, headers, and libraries to perform
the builds and execution, calling proprietary interfaces to support POSIX.
> So, enabling CUDA support in pocl should also be allowed, I think.
I believe not if the Nvidia tools do not have sources available to build with
Cygwin tools built from sources.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2024-01-03 12:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 5:14 Takashi Yano
2024-01-03 5:25 ` Takashi Yano
2024-01-03 7:54 ` Marco Atzeri
2024-01-03 9:29 ` Takashi Yano
2024-01-03 11:38 ` Brian Inglis
2024-01-03 12:00 ` Takashi Yano
2024-01-03 12:26 ` Brian Inglis [this message]
2024-01-03 12:42 ` Takashi Yano
2024-01-03 12:30 ` Takashi Yano
2024-01-03 14:08 ` Takashi Yano
2024-01-04 0:55 ` Takashi Yano
2024-01-13 15:48 ` Jon Turney
2024-01-14 14:57 ` Takashi Yano
2024-01-14 20:46 ` Jon Turney
2024-01-15 3:14 ` Takashi Yano
2024-01-07 12:51 ` Jon Turney
2024-01-07 13:05 ` Takashi Yano
2024-01-08 0:38 ` Andrew Schulman
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=19a0d8be-a17e-438f-bf3b-71ddd7cafee9@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.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).