Date: Thu, 7 Dec 2023 02:46:35 -0800 From: Mark Millard <marklmi@yahoo.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: Warner Losh <imp@bsdimp.com>, Current FreeBSD <freebsd-current@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, dan@langille.org, Mike Karels <mike@karels.net> Subject: Re: aarch64 and armv6 vs. armv7 support: armv6 is not supported, despite what "man arch" reports Message-ID: <1B672854-4011-4F4D-BFBC-4C3ABF6FA4FB@yahoo.com> In-Reply-To: <2F5E2EA1-246A-4098-A964-3C8DEA2EF297@FreeBSD.org> References: <3C33BBA5-A84D-4F46-B38E-B67F9FE0196D.ref@yahoo.com> <3C33BBA5-A84D-4F46-B38E-B67F9FE0196D@yahoo.com> <2F5E2EA1-246A-4098-A964-3C8DEA2EF297@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Dec 7, 2023, at 01:19, Dimitry Andric <dim@FreeBSD.org> wrote: > On 7 Dec 2023, at 05:31, Mark Millard <marklmi@yahoo.com> wrote: >> >> man arch reports: >> >> QUOTE >> Some machines support more than one FreeBSD ABI. Typically these are >> 64-bit machines, where the “native” LP64 execution environment is >> accompanied by the “legacy” ILP32 environment, which was the historical >> 32-bit predecessor for 64-bit evolution. Examples are: >> >> LP64 ILP32 counterpart >> amd64 i386 >> powerpc64 powerpc >> aarch64 armv6/armv7 > > So, this might be replaced with "armv6^armv7" or "armv6 xor armv7", then? Only for folks that build from source. For those folks, a footnote about updating MACHINE_ARCH32 in sys/arm64/include/param.h would be appropriate. It is not exactly obvious or commonly known. Hmm, thinking more about the old bugzilla information . . . I'll also note that my information predated lib32 on aarch64: just chroot/jail sorts of use back then, and I just tested chroot back then. I've never tested a lib32 context for armv6 on aarch64 for an adjusted MACHINE_ARCH32. === Mark Millard marklmi at yahoo.comhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1B672854-4011-4F4D-BFBC-4C3ABF6FA4FB>