3 ms·

Tell that the big vendors. Only mingw AFAIK ships i686 packages (with simd support), all others stay in the safe i386 camp still, without simd support.

by rurban 3y ago

westurner 3y ago
Gentoo ebuild USE and CFLAGS flags allow the user to specify custom compilation settings as necessary for optimization on a given processor architecture like i386, i486, i586, or i686. For example, with ebuild (or dpkg-repack or rpmrebuild) a person could build the compiler packages with all of the appropriate optimization flags for the chipset on the box where the package will be installed: https://packages.gentoo.org/useflags/custom-cflags https://packages.gentoo.org/useflags/custom-cflags Cross-compilation is easier with clean build containers. With distrobox (and qemu, qemu-user-static, and binfmt-support) https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-a-different-architecture https://github.com/89luca89/distrobox/blob/main/docs/useful_... : $ uname -m x86_64 $ distrobox create -i aarch64/fedora -n fedora-arm64 $ distrobox enter fedora-arm64 user@fedora-arm64:$ uname -m aarch64
zokier 3y ago
Afaik Debian is fully i686 these days: https://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#i386-is-i686 https://www.debian.org/releases/stable/i386/release-notes/ch...
dralley 3y ago
Fedora ships i686 packages. At least that's what they're called.
unleaded 3y ago
Linux kernel hasn't supported 386 for over 10 years, I don't think there's any reason for them to do that
numpad0 3y ago
Linux dropped support for real 80386 a decade ago in 3.8, so `Linux > 3.8` and `CPU model == Intel 80386` are mutually exclusive. Whatever i386 is supposed to be, it's something more modern. 1: https://www.phoronix.com/news/MTI0OTg https://www.phoronix.com/news/MTI0OTg
wtallis 3y ago
> Only mingw AFAIK ships i686 packages (with simd support), all others stay in the safe i386 camp still, without simd support. Conflating i686 vs i386 with SIMD vs no SIMD is wrong. The Pentium Pro was an i686 processor with no SIMD, and the Pentium 2 was its successor that added MMX — a very narrowly-useful integer-only SIMD extension (which was first introduced on the pre-i686 Pentium MMX). Floating point SIMD (SSE) didn't show up until the Pentium 3 (on the Intel side; AMD's 3DNow was earlier but was eventually dropped). It's certainly reasonable to enable SSE and SSE2 when building for 32-bit x86 these days, but calling that target "i686" doesn't accurately describe the hardware requirements.

Tell that the big vendors. Only mingw AFAIK ships i686 packages (with simd support), all others stay in the safe i386 camp still, without simd support.

by rurban 3y ago

Tell that the big vendors. Only mingw AFAIK ships i686 packages (with simd support), all others stay in the safe i386 camp still, without simd support.

westurner 3y ago

Gentoo ebuild USE and CFLAGS flags allow the user to specify custom compilation settings as necessary for optimization on a given processor architecture like i386, i486, i586, or i686. For example, with ebuild (or dpkg-repack or rpmrebuild) a person could build the compiler packages with all of the appropriate optimization flags for the chipset on the box where the package will be installed: https://packages.gentoo.org/useflags/custom-cflags https://packages.gentoo.org/useflags/custom-cflags Cross-compilation is easier with clean build containers. With distrobox (and qemu, qemu-user-static, and binfmt-support) https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-a-different-architecture https://github.com/89luca89/distrobox/blob/main/docs/useful_... : $ uname -m x86_64 $ distrobox create -i aarch64/fedora -n fedora-arm64 $ distrobox enter fedora-arm64 user@fedora-arm64:$ uname -m aarch64

zokier 3y ago

Afaik Debian is fully i686 these days: https://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#i386-is-i686 https://www.debian.org/releases/stable/i386/release-notes/ch...

dralley 3y ago

Fedora ships i686 packages. At least that's what they're called.

unleaded 3y ago

Linux kernel hasn't supported 386 for over 10 years, I don't think there's any reason for them to do that

numpad0 3y ago

Linux dropped support for real 80386 a decade ago in 3.8, so `Linux > 3.8` and `CPU model == Intel 80386` are mutually exclusive. Whatever i386 is supposed to be, it's something more modern. 1: https://www.phoronix.com/news/MTI0OTg https://www.phoronix.com/news/MTI0OTg

wtallis 3y ago

> Only mingw AFAIK ships i686 packages (with simd support), all others stay in the safe i386 camp still, without simd support. Conflating i686 vs i386 with SIMD vs no SIMD is wrong. The Pentium Pro was an i686 processor with no SIMD, and the Pentium 2 was its successor that added MMX — a very narrowly-useful integer-only SIMD extension (which was first introduced on the pre-i686 Pentium MMX). Floating point SIMD (SSE) didn't show up until the Pentium 3 (on the Intel side; AMD's 3DNow was earlier but was eventually dropped). It's certainly reasonable to enable SSE and SSE2 when building for 32-bit x86 these days, but calling that target "i686" doesn't accurately describe the hardware requirements.