[GH-ISSUE #30] Failed to compile on the aarch64 architecture. #20

Open
opened 2026-10-26 09:43:31 +00:00 by bsakaguchi · 3 comments
Owner

Originally created by @RainSnowIceRain on GitHub (Mar 1, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/30

Why was the static assertion static_assert(x86_64, "The platform must be 64bit!"); added at line 104 in the file src/common/utils/Status.h? Does this imply that the code is not supported for deployment on machines with the aarch64 architecture?

Originally created by @RainSnowIceRain on GitHub (Mar 1, 2025). Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/30 Why was the static assertion static_assert(__x86_64__, "The platform must be 64bit!"); added at line 104 in the file src/common/utils/Status.h? Does this imply that the code is not supported for deployment on machines with the aarch64 architecture?
Author
Owner

@dylangerdaly commented on GitHub (Mar 1, 2025):

C'monnnnnn, pls support aarch64.

<!-- gh-comment-id:2692347514 --> @dylangerdaly commented on GitHub (Mar 1, 2025): C'monnnnnn, pls support aarch64.
Author
Owner

@SF-Zhou commented on GitHub (Mar 2, 2025):

In the Status struct, we utilize the high 16 bits of 64-bit pointers to store status codes. This feature is available on x86_64 architectures and most aarch64 architectures (like folly/PackedSyncPtr). While we plan to remove restrictions for aarch64 architectures, our production environment currently only has x86_64 machines, making it impossible to test compilation and runtime behavior on aarch64. We welcome any feedback!

<!-- gh-comment-id:2692490771 --> @SF-Zhou commented on GitHub (Mar 2, 2025): In the Status struct, we utilize the high 16 bits of 64-bit pointers to store status codes. This feature is available on x86_64 architectures and most aarch64 architectures (like [folly/PackedSyncPtr](https://github.com/facebook/folly/blob/main/folly/PackedSyncPtr.h#L26)). While we plan to remove restrictions for aarch64 architectures, our production environment currently only has x86_64 machines, making it impossible to test compilation and runtime behavior on aarch64. We welcome any feedback!
Author
Owner

@Nugine commented on GitHub (Mar 2, 2025):

GitHub Actions provides aarch64 linux runners for free. It's possible to test compilation on an aarch64 runner.

<!-- gh-comment-id:2692575805 --> @Nugine commented on GitHub (Mar 2, 2025): GitHub Actions provides [aarch64 linux runners for free](https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/). It's possible to test compilation on an aarch64 runner.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/3FS#20
No description provided.