Description
The google-antigravity package (v0.1.7) ships a native Go binary in the manylinux_2_17_x86_64 wheel that is compiled with AVX instruction set support (GOAMD64=v3). This causes an immediate crash on x86-64 CPUs that do not support AVX instructions.
Error Message
FATAL ERROR: This binary was compiled with avx enabled, but this feature is not available on this processor (go/sigill-fail-fast)
Affected Hardware
This affects a significant class of x86-64 processors that lack AVX support, including:
- Intel Celeron (J3455, J4125, N5105, etc.) — commonly found in NAS devices
- Intel Atom series
- Older Intel Xeon and Core processors (pre-Haswell, before 2013)
- Some AMD processors (pre-Bulldozer)
These processors are widely used in home servers, NAS appliances (Synology, QNAP), and budget server hardware.
Steps to Reproduce
- Install
google-antigravity on a machine with a CPU without AVX support (e.g., Synology NAS with Intel Celeron J3455)
- Import and use the package:
from google.antigravity import Agent
- The process crashes with
SIGILL (Illegal Instruction)
Expected Behavior
The package should work on any x86-64 processor, or at minimum provide a clear error message suggesting hardware requirements.
Suggested Fix
Compile the Go binary with GOAMD64=v1 (baseline x86-64, no AVX/AVX2/SSE4 requirements) instead of GOAMD64=v3. This would ensure compatibility with all x86-64 processors while maintaining full functionality (with a minor performance trade-off on newer hardware).
Alternatively, consider shipping two wheel variants:
manylinux_2_17_x86_64 — baseline build (GOAMD64=v1)
- An optimized variant for modern CPUs
Context
This issue was reported by a user of paperless-genie (which depends on google-antigravity) running Docker on a Synology NAS: rabestro/paperless-genie#79.
Environment
google-antigravity version: 0.1.7
- Wheel:
google_antigravity-0.1.7-py3-none-manylinux_2_17_x86_64.whl
- OS: Debian Bookworm (Docker container)
- CPU: Intel Celeron (no AVX support)
Description
The
google-antigravitypackage (v0.1.7) ships a native Go binary in themanylinux_2_17_x86_64wheel that is compiled with AVX instruction set support (GOAMD64=v3). This causes an immediate crash on x86-64 CPUs that do not support AVX instructions.Error Message
Affected Hardware
This affects a significant class of x86-64 processors that lack AVX support, including:
These processors are widely used in home servers, NAS appliances (Synology, QNAP), and budget server hardware.
Steps to Reproduce
google-antigravityon a machine with a CPU without AVX support (e.g., Synology NAS with Intel Celeron J3455)SIGILL(Illegal Instruction)Expected Behavior
The package should work on any x86-64 processor, or at minimum provide a clear error message suggesting hardware requirements.
Suggested Fix
Compile the Go binary with
GOAMD64=v1(baseline x86-64, no AVX/AVX2/SSE4 requirements) instead ofGOAMD64=v3. This would ensure compatibility with all x86-64 processors while maintaining full functionality (with a minor performance trade-off on newer hardware).Alternatively, consider shipping two wheel variants:
manylinux_2_17_x86_64— baseline build (GOAMD64=v1)Context
This issue was reported by a user of paperless-genie (which depends on
google-antigravity) running Docker on a Synology NAS: rabestro/paperless-genie#79.Environment
google-antigravityversion: 0.1.7google_antigravity-0.1.7-py3-none-manylinux_2_17_x86_64.whl