Date: Sun, 7 May 2023 17:10:14 -0600 From: Rebecca Cran <rebecca@bsdio.com> To: Jessica Clarke <jrtc27@freebsd.org>, Hans Petter Selasky <hps@selasky.org> Cc: freebsd-arch <freebsd-arch@freebsd.org>, John Baldwin <jhb@FreeBSD.org> Subject: Re: Future of 32-bit platforms (including i386) Message-ID: <5b809b1e-24d2-1654-824c-f8367d7ef0d5@bsdio.com> In-Reply-To: <A260039D-B51F-4593-9A85-8A5CF2818DEF@freebsd.org> References: <aaa3e005-5f72-f422-56b1-932842379e15@FreeBSD.org> <671d3bf6-b207-e7c5-5282-4df317193db6@selasky.org> <A260039D-B51F-4593-9A85-8A5CF2818DEF@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/27/23 17:50, Jessica Clarke wrote: > I don’t know where to start with this other than to give an emphatic no to almost all of what you said, or at least the bits for which meaning can be extracted. Regardless, this is not the place for such pie-in-the-sky discussions; if you want to theorise about weird and wacky computer architectures then please take it elsewhere. It's hard enough to get it right when there's a single instruction set, as with Arm's big.LITTLE. For example: https://www.mono-project.com/news/2016/09/12/arm64-icache/ I've also heard of problems of programs crashing due to instructions supported on one core type not being supported on the other. -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5b809b1e-24d2-1654-824c-f8367d7ef0d5>