mgorny-nyan (he) :autism:🙀🚂🐧 on Nostr: What people usually think breaks software on #32-bit architectures: • different ...
What people usually think breaks software on #32-bit architectures:
• different integer type sizes (actually, out of standard integer types, only `long` is different, and people rarely use that these days)
What actually breaks software on 32-bit architectures:
• building without Large File Support (this is also required for 64-bit inode numbers)
• 32-bit `time_t` (and the resulting y2k38 problem)
• allocating egregious amounts of memory (even if you aren't going to use them, address space is limited)
• (on x86) 80-bit floating point arithmetic (unless you're doing `-mfpmath=sse`, then 64-bit floating arithmetic when apps were special-casing x86…)
#portability #Gentoo
• different integer type sizes (actually, out of standard integer types, only `long` is different, and people rarely use that these days)
What actually breaks software on 32-bit architectures:
• building without Large File Support (this is also required for 64-bit inode numbers)
• 32-bit `time_t` (and the resulting y2k38 problem)
• allocating egregious amounts of memory (even if you aren't going to use them, address space is limited)
• (on x86) 80-bit floating point arithmetic (unless you're doing `-mfpmath=sse`, then 64-bit floating arithmetic when apps were special-casing x86…)
#portability #Gentoo