From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2203015802E for ; Wed, 26 Jun 2024 21:08:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9508EE2B8B; Wed, 26 Jun 2024 21:08:23 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D6A61E2B88 for ; Wed, 26 Jun 2024 21:08:22 +0000 (UTC) From: "Andreas K. Huettel" To: gentoo-dev@lists.gentoo.org Cc: Arthur Zamarin Subject: 32bit vs 64bit, was: Re: [gentoo-dev] Arch Status and Future Plans Date: Wed, 26 Jun 2024 23:08:15 +0200 Message-ID: <1979795.yKVeVyVuyW@pinacolada> Organization: Gentoo Linux In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2150453.OBFZWjSADL"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Archives-Salt: 5b26734c-ddc2-4991-9a9f-6e8241eb0c6e X-Archives-Hash: 51800fb75e33b7ca63db14b59b7f8e88 --nextPart2150453.OBFZWjSADL Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1" From: "Andreas K. Huettel" To: gentoo-dev@lists.gentoo.org Cc: Arthur Zamarin Date: Wed, 26 Jun 2024 23:08:15 +0200 Message-ID: <1979795.yKVeVyVuyW@pinacolada> Organization: Gentoo Linux In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> MIME-Version: 1.0 > =3D=3D=3D=3D=3D=3D=3D=3D 32-bit arches =3D=3D=3D=3D=3D=3D=3D=3D >=20 > This includes stable arches x86, arm, ppc, sparc32, dev arches s390, and > maybe more. Those are in much worse situation, with a mess on various > fronts, some of them super hard to continue support. For example > qtwebengine is less and less likely to manage to compile on a > real-hardware, and not 32-bit chroot on 64-bit host. Arch Team want to > minimize our work on those arches, meaning mass-destable and even > mass-dekeyword, with potentially full drop of stable status. We've got several different types of problems here. 1) Different data type sizes This is the least problematic point, since testing in a chroot works fine. 2) Limitations, e.g. limited memory address space Also not that problematic, since testing in a chroot on a 64bit kernel circumvents the limitation somewhat. Whether it makes sense to be able to build something in a chroot but never= =20 on real hardware is another question. 3) time64 This is work in progress. I guess we'll get it done until 2038. 4) isa- and hardware-related regressions. This is the real problem that cannot be caught via chroots and testing on fast 64bit machines... We recently had an upstream regression in glibc that (from memory) broke all machines without SSE. It took a surprisingly long time for anyone to notice that, since of course any x86-64 machine understands these=20 instructions. The only way to really reproduce it on modern hardware is in qemu-system with disabled kvm. Can we call an architecture "stable" if we never test on real (and not "downward-emulated") hardware? =2D-=20 Andreas K. H=FCttel dilfridge@gentoo.org Gentoo Linux developer (council, toolchain, base-system, perl, libreoffice) --nextPart2150453.OBFZWjSADL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQKTBAABCgB9FiEE/Rnm0xsZLuTcY+rT3CsWIV7VQSoFAmZ8gz9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZE MTlFNkQzMUIxOTJFRTREQzYzRUFEM0RDMkIxNjIxNUVENTQxMkEACgkQ3CsWIV7V QSp9tRAAlONrXmlwrKJ1Ir3/hwM67WE6DEqKVy+N6DS3LYll8ObHXD3BUZrJ1nkR JcaoTUqiScXHtzw1PNGlo/RRtGUMHhff3ufIm6slt/BmmJfgcFuf5Wyb0n+1KaCt nYMdl9SBqecQ2RFRXEkBqCyNpvIqoZ8VdZ3YTmLa84pHcUbY/SdCoK+XRuV3shw9 /+KYheUW8p/hAFbbhAOoaBVn6ZkPRs9Tq12YFxHOYx8xAHUCbKlmv5Xo3lWBrdaa mDLsONOgkBymxScqlhvMHarFJRPq4eJYo6rc4qik4eKOS+PYnsn2uUj0fI3jpIyN e1+4eaZLONXewB7rhUJ/F3eR/g5WRCREn1pNcwCInGwFz9ZkVV1VSxcz27bL654I JXQz1l1O9QTg/ZPK4yAHFT86oIRkHktwGjBk0cqO4KDaUCdqXgM5zE6VL1FEou1I L4RIPFeKKPaPCN5uZEwcFmfAod8eDYbxoI3fIs9Gg2zatabHIe5eEse2ly1zRat7 wGk5EPIrcqv/ngB1ZO224qhb2YkTjZbRT95uwI7cap760PAdweZrs9o4tuCAcMAC jgYlYTzqnGE/BaELDqy0h7olB0SJ2zZixUuqx6dd13C7JyO7hXDD/SsyP+HS55f/ NTVOdavQHVbx1m6NEPB7nNJI4x1ELpp6RCroCUTGMg32S+486Zs= =1vDT -----END PGP SIGNATURE----- --nextPart2150453.OBFZWjSADL--