all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Fis Trivial <ybbs.daans@hotmail.com>
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: 31436@debbugs.gnu.org
Subject: [bug#31436] [PATCH 0/6] gnu: Add opencl related packages.
Date: Sat, 26 May 2018 17:42:58 +0000	[thread overview]
Message-ID: <BLUPR16MB05009B1D7AC04C6DCDC8978492680@BLUPR16MB0500.namprd16.prod.outlook.com> (raw)
In-Reply-To: <BLUPR16MB0500D0852942A2CF69BC740D929E0@BLUPR16MB0500.namprd16.prod.outlook.com>


Fis Trivial writes:

> 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.
>

Hi, guixs.

Sorry.

I don't think any usable OpenCL implementation in guix can be done in
recent future. OpenCL is kind of deeply integrated with clang and
llvm. One of the problem of this integration is that ld is not invoked
with correct search path. And usually the link procedure is implemented
by calling llvm APIs since ld doesn't know how to link device binary
objects. Which means if we want to solve this problem we will have to
figure out how does llvm do linking and add the corresponding patches to
make a specialized llvm. If I were to do it, I would rather try to get
ld and gcc support basic OpenCL linking, the needed effort is not that
different.

You can still review these packages without pocl and beignet (these two
are implementation), so that others who want to enable OpenCL in guix
will not have to packages those headers and helper tools.

  parent reply	other threads:[~2018-05-26 17:44 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 ` Fis Trivial [this message]
2018-05-28 12:51   ` [bug#31436] [PATCH 0/6] gnu: Add opencl related packages Ludovic Courtès
2018-06-25 20:22 ` Ludovic Courtès
2018-06-25 20:58   ` Fis Trivial
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=BLUPR16MB05009B1D7AC04C6DCDC8978492680@BLUPR16MB0500.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=31436@debbugs.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.