Lack of AVX-512 causing installation errors while installing Executorch
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
Issue: Lack of AVX-512 on our CPU causing installation errors while installing Executorch on main and viable/strict branch.
Resolution: Redefine _mm_loadu_si64 and _mm_storeu_si64 to their safe AVX2-compatible equivalents using compiler flags. The command used was
CFLAGS="-D_mm_loadu_si64=_mm_loadl_epi64 -D_mm_storeu_si64=_mm_storel_epi64”
CXXFLAGS="-D_mm_loadu_si64=_mm_loadl_epi64 -D_mm_storeu_si64=_mm_storel_epi64"
./install_executorch.sh |& tee executorch_installation.log
Commenting out XNNPACK does not resolve the issue.
Is AVX-512 a requirement for executorch installation? If so, is it documented somewhere?
Thanks
@zonglinpengmeta @mcremon-meta
cc @digantdesai @mcr229 @cbilgin
Contributor guide
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.
Research direction
Start with install_executorch.sh and the installation behavior on the main and viable/strict branches. Check whether AVX-512 is required and how the provided CFLAGS and CXXFLAGS workaround affects installation on CPUs without it. Done means the requirement and any supported workaround are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, shell
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100