all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Fis Trivial <ybbs.daans@hotmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "31436@debbugs.gnu.org" <31436@debbugs.gnu.org>
Subject: [bug#31436] [PATCH 0/6] gnu: Add opencl related packages.
Date: Mon, 25 Jun 2018 20:58:59 +0000	[thread overview]
Message-ID: <SN1PR16MB0511A56AD2D6DEB7AEF2C212924A0@SN1PR16MB0511.namprd16.prod.outlook.com> (raw)
In-Reply-To: <87o9fyr502.fsf@gnu.org>


Ludovic Courtès writes:

> Hello Fis!
>
> Fis Trivial <ybbs.daans@hotmail.com> skribis:
>
>> These patches add basic support for opencl. As noted in the new file
>> opencl.scm, tests can't enabled by now. For the future, maybe we can
>> patch the build system to make test targets installable so that people
>> with right tools can help testing. Or maybe there are some other ways
>> that we can modify the build environment for testing. But that's another
>> day's problem. :)
>>
>> Although testing with packages' unit tests are not enabled. I tried to
>> test them outside the store by simple hello world program, they works
>> fine on my hardware.
>>
>> To make thing a little comfortable, I packaged clinfo, which is a little
>> tool for displaying OpenCL platforms and device information by calling
>> OpenCL host functions. If it works on your device, then at least you can
>> confirm the corresponding implementation is not completely broken.
>>
>> Environment variable `OPENCL_VENDOR_PATH` is used to guide `ocl-icd`
>> loading needed OpenCL implementation library. You need to source it in
>> your profile before you try to use any of the implementation.
>>
>> I wrapped clinfo, notes are put in the package definition.
>>
>>
>> fis (6):
>>   gnu: Add opencl-headers.
>>   gnu: Add opencl-clhpp.
>>   gnu: Add ocl-icd.
>>   gnu: Add beignet.
>>   gnu: Add clinfo.
>>   gnu: Add pocl.
>
> I finally applied the first two patches.
>
> Could you remind me what the blocker is for the subsequent patches?  I
> know we discussed it but I couldn’t find the details.
>
> Thanks, and sorry for the delay!
>
> Ludo’.

For POCL. The problem is ld couldn't find the right path. Another one is
Guix currently doesn't have any modern GPU support due to firmware
blobs. So OpenCL here is not very attractive in general unless one
maintain his/her own kernel. Or maybe someone here toys with FPGA? :)

Beignet is now deprecated in favor the new Neo project (both are from
Intel).

Jiaming

  reply	other threads:[~2018-06-25 21:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-12 19:46 [bug#31436] [PATCH 0/6] gnu: Add opencl related packages Fis Trivial
2018-05-12 19:49 ` [bug#31436] [PATCH 1/6] gnu: Add opencl-headers Fis Trivial
2018-05-12 19:49 ` [bug#31436] [PATCH 2/6] gnu: Add opencl-clhpp Fis Trivial
2018-05-12 19:50 ` [bug#31436] [PATCH 3/6] gnu: Add ocl-icd Fis Trivial
2018-05-12 19:50 ` [bug#31436] [PATCH 4/6] gnu: Add beignet Fis Trivial
2018-05-12 19:51 ` [bug#31436] [PATCH 5/6] gnu: Add clinfo Fis Trivial
2018-05-12 19:52 ` [bug#31436] [PATCH 6/6] gnu: Add pocl Fis Trivial
2018-05-26 17:42 ` [bug#31436] [PATCH 0/6] gnu: Add opencl related packages Fis Trivial
2018-05-28 12:51   ` Ludovic Courtès
2018-06-25 20:22 ` Ludovic Courtès
2018-06-25 20:58   ` Fis Trivial [this message]
2018-06-26 13:44     ` Ludovic Courtès
2018-06-26 18:49       ` Fis Trivial
2018-06-26 19:37       ` [bug#31436] [PATCH 0/3] Resend some opencl packages Fis Trivial
2018-06-26 19:39       ` [bug#31436] [PATCH 1/3] gnu: Add ocl-icd Fis Trivial
2018-06-26 20:26         ` Ludovic Courtès
2018-06-26 20:57           ` Fis Trivial
2018-06-26 19:39       ` [bug#31436] [PATCH 2/3] gnu: Add clinfo Fis Trivial
2018-06-26 20:32         ` Ludovic Courtès
2018-06-26 19:40       ` [bug#31436] [PATCH 3/3] gnu: Add beignet Fis Trivial
2018-06-26 21:00         ` bug#31436: " Ludovic Courtès

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=SN1PR16MB0511A56AD2D6DEB7AEF2C212924A0@SN1PR16MB0511.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=31436@debbugs.gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.