Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binary release names are misleading, specially x32 #24572

Open
arnetheduck opened this issue Dec 27, 2024 · 0 comments
Open

Binary release names are misleading, specially x32 #24572

arnetheduck opened this issue Dec 27, 2024 · 0 comments

Comments

@arnetheduck
Copy link
Contributor

Description

x32 means 32-bit pointers on 64-bit CPU and is used to save memory on 64-bit systems that come with less than 4gb of memory. x64 is kind of better, but the proper name for this one is usually x86_64.

As is, the names are neither derived from the --cpu flag (whose values are nim-specific and therefore less useful in the toolchain world), nor does it match "target triples" (what modern toolchains uses) - any of these two sources would be an improvement on the status quo - ie amd64 vs x86_64, with a preference for the latter since that would move us in a direction of simplifying interaction with the rest of the toolchain world.

Further, this would also set a standard that all "binary tools" can use (nimble etc), so that tool-platform.tar.gz becomes a "standard" name for getting a binary release of tool.

Nim Version

....

Current Output

No response

Expected Output

No response

Known Workarounds

No response

Additional Information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant