Builds of Velox fail in system with ARM-SVE but Builds of Gluten do not
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 657
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 80
Description
### Problem description
While building Velox on a system with ARM-SVE, the build fails due to a lack of explicit support for SVE in Velox, which is understandable since Velox's documentation does not mention SVE support.
However, when using Gluten, which relies on Velox as its backend, the build does not fail, even though no SVE-related code exists in Gluten itself.
I would like to know these:
1) Why does Gluten not fail to build when Velox (the backend) does, given the same system configuration?
2) If SVE-related optimizations are added to Gluten code repo, would the build still succeed, or would it encounter issues due to Velox's lack of support for SVE?
### System information
Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Vendor ID: ARM
Model: 1
Thread(s) per core: 1
Core(s) per socket: 16
Socket(s): 1
Stepping: r1p1
BogoMIPS: 2100.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp
cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha51
2 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei
8mm svebf16 i8mm bf16 dgh rng
Gluten Version: 1.3.0-SNAPSHOT
Commit: Not in a git repo.
CMake Version: 3.28.3
System: Linux-6.8.0-1021-aws
Arch: aarch64
CPU Name:
C++ Compiler: /usr/bin/c++
C++ Compiler Version: 11.4.0
C Compiler: /usr/bin/cc
C Compiler Version: 11.4.0
CMake Prefix Path: /usr/local;/usr;/;/usr/local/lib/python3.10/dist-packages/cmake/data;/usr/local;/usr/X11R6;/usr/pkg;/opt
### CMake log
_No response_
Contributor guide
Research direction
Start by reproducing the ARM-SVE build with the reported CMake, compiler, and system details, then compare the Velox and Gluten configuration and dependency logs. Done means documenting why their builds differ and whether adding SVE code to Gluten changes compatibility with Velox; no source files or tests are identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, linux
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100