New packages - Intel OpenCL (NEO)

[zlice]

[ci skip]

Testing the changes

• I tested the changes in this PR: YES

Ran a few OpenCL examples and cl-mem. clinfo reports more stats also

New package

• This new package conforms to the package requirements: YES

Local build testing

• I built this PR locally for my native architecture, x86_64

Could not get musl to build intel-compute-runtime. There are a few patches for execinfo, backtrace and RTLD_XXX but even sorting those out gets to a 'error code: -11'.

Comments

closes #11364

depends on #41132 for gmmlib bump (didn't want to add there in case it delays merge)

MIT license not in the tar for intel-vc-intrinsics yet? Was just added the other day.

level-zero uses git to pull spdlog(1.13.0). Void does not have a 'spdlog-devel' but it could probably be added.

Update (ready)

Added llvm14 with the SWIG patches and musl builds (with a few more patches)

llvm 14 has a shlib of libclang.so.13 libclang14-14.0.6_1 for some reason, it works, it should only be for these packages on x86_64+musl

[zlice]

Apparently this takes too much space to build, looks like it was killed - g++: fatal error: Killed signal terminated program cc1plus.

[ja-cop]

Just curious, do you happen to know how this relates to oneAPI and "level zero"? I'd love to use the oneAPI support in Blender for hardware accelerated Cycles, but even after installing intel-compute-runtime from this PR, Blender says:

Is this out of scope of this PR? Also, maybe it's because Blender is running in Flatpak? Void's Blender doesn't show the oneAPI tab, I guess it's compiled out or something.

[zlice]

I think I originally had a level-zero package but it looked like nothing used it. Can take another look and try to see if Blender picks anything up. Need to bump this anyway. Hopefully sometime tomorrow.

[zlice]

I added level-zero back, that may be enough for the Flatpak to pick up ?

But it looks like building Blender with CYCLES_OPENAPI requires SYCL and a bunch of Intel ONEAPI packages for compilers. Not sure what all is involved, looks like a lot. Don't feel great about adding to this.

Good news for me though, Blender 3.5 doesn't need ffmpeg6 patches :)

blender_template.txt

sycl_template.txt

[ja-cop]

Unfortunately, installing level-zero from here wasn't enough to get Blender from Flatpak to pick up the GPU. I tried having a look around the Blender source code for loading oneAPI but I still don't really understand it. I think I'll ask over at the Blender Flatpak issue tracker to see if anyone knows how this is supposed to work.

---

I got your Blender and SYCL templates building, and it in Cycles Render Devices, it shows CUDA and HIP, but OptiX and oneAPI are missing compared to the Flatpak version.

Thanks a lot for the help, though! \o/

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

[zlice]

still waiting on #41132

[cy1der]

Apologies in advance if this is the wrong place for this.

But I can't seem to install this, it's failing at compiling intel-compute-runtime, the rest was fine. Looks like its complaining about Raptor Lake or something...

Here's the logs of do_build:
do_build.txt

If it matters at all, I'm on an i7-8665U.

[zlice]

Here's the logs of do_build: do_build.txt

sry for late reply. still builds fine for me, just did a clean rebuild. i remember getting those types of errors and i think it was gmmlib not being updated before.

[zlice]

Updated version and verified the cl-mem example still works.

Bumped oneVPL, intel-media-driver and intel-gmmlib. Can put those in different PRs if it matters. (also oneVPL is now 'libvpl' and has a version change that is lower... didn't mess with that as I didn't see a difference with a quick test or anything important on the release page)

[zlice]

intel/media-driver@632f240

Should be good for musl now. Will try to do arm/musl mix builds in a day or few.

[zlice]

intel/intel-graphics-compiler#332

intel-graphics-compile not working for musl

[zlice]

Sounds like only llvm14 is officially supported. 14 was never in void (12 -> 15) and trying to build it falls to some 'swig' error? https://forums.gentoo.org/viewtopic-p-8755491.html?sid=216b6b968a7d942265029bf44921e1b0

Removed archs=x86_64* for musl. Not sure who is using musl for Intel openCL but for now I guess it's not doable unless someone else can figure out what's segfaulting and fix it. (See the above issue for vcb failing)

[Calandracas606]

this is neat.

I'm probably going to version the spirv translator in llvm19, so it's good that you did it here

[Calandracas606]

there's a lot of junk in the llvm14 package that's only needed for cross compiling. if its x86_64 only, you can safely remove it

[zlice]

ya i can remove it. afaik intel only supports x86_64 and i dont think anyone would try to use some intel gpu in a arm box anyway. will update once the vpl stuff goes through because i'm lazy and dont want to build llvm extra if i dont have to

[Calandracas606]

look at the SPIRV-LLVM-Translator changes here: https://github.com/void-linux/void-packages/pull/51592/files

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.