SYCL build fails on Intel Arc A770 (Alchemist) - v0.1.40.1
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cpp
- Domain
- backend, build-system
Research direction
Start with the two named errors: in sycl/src/kernels/cuda/fused_gr.dp.cpp around line 1607 reconcile the void definition with the bool declaration in its header (find the header by including/searching the declared prototype), and in sycl/src/core/expert_source.cpp line 2938 resolve the ambiguous load_experts_gguf call by locating both conflicting definitions and removing or disambiguating the duplicate. Done looks like cmake --build build-sycl --target strata completing with icx/icpx; note verification needs the oneAPI DPC++ toolchain, so check whether further architecture-specific errors appear in the full log.
Written by the indexing model from the issue text.
Description
Building the SYCL engine on CachyOS with an Intel Arc A770 (Alchemist) fails with multiple errors.
Environment:
- OS: CachyOS (Arch-based)
- Kernel: 7.2.6-1-cachyos
- GPU: Intel Arc A770 (DG2/Alchemist)
- Driver: xe (Kernel driver in use: xe)
- oneAPI DPC++/C++ Compiler: 2026.1.1
- Strata version: v0.1.40.1 (commit 82f46a8)
Build command:
cmake -S sycl -B build-sycl -G Ninja -DCMAKE_C_COMPILER=icx -DCMAKE_CXX_COMPILER=icpx -DSTRATA_SYCL_PARITY=OFF
cmake --build build-sycl --target strata
Errors (from build log):
-
fused_gr.dp.cpp:
/home/javal/Strata/sycl/src/kernels/cuda/fused_gr.dp.cpp:1607:6: error: functions that differ only in their return type cannot be overloaded
(definition isvoid, header declaresbool) -
expert_source.cpp:
/home/javal/Strata/sycl/src/core/expert_source.cpp:2938:14: error: call to 'load_experts_gguf' is ambiguous
(two conflicting definitions)
Full build log: (attach /tmp/strata_build_v0140.log)
The Alchemist (A770) architecture is not listed as tested in docs/INTEL_ARC.md. It seems the SYCL port has compilation issues that are specific to this architecture.
- Dominant language
- C++
- Stars
- 11.6k
- Forks
- 1k
- Avg merge
- 7h 46m
- Merged PRs (30d)
- 30
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Niko1221/Strata
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
bug iOS 🍎 ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4744 ·
Maintainers usually reply within 1 day
-
Component: Ruby Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
kokkos/kokkos-kernels#3328 ·
Maintainers usually reply within 1 day
-
bug needs triage tcp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
project-chip/connectedhomeip#74644 ·
Maintainers usually reply within 1 day