You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 usuallyx86_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 - ieamd64
vsx86_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 oftool
.Nim Version
....
Current Output
No response
Expected Output
No response
Known Workarounds
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: