Consider making 32 bit builds for background packages? #232
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#232
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I understand if you don't want to do this for maintenance burden, if so, just close this issue.
A large amount of services are never going to use 2-4gb of ram, so idle memory usage could seriously benefit from building with 32 bit pointers. This would also benefit performance as less memory usage leads to less cache pressure, less swapping, and less instructions needed to manipulate pointer data. If a list of packages could be made of executables that would never need the extra address space so could be built as 32 bit pointers with 64 bit feature set, that would be a dream come true.
A massive downside is that it requires 32 bit packages all the way down, for libraries, but this should be possible as you already have the buildbot to do this.
I am pretty sure compilers are able to produce this combination, I know Rust can definitely with the i686 target and the target-cpu value being set to 64 bit instruction set levels.