Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6jWs-00F9YC-82 for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Nov 2024 04:44:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t6jWq-009Ezc-6G for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Nov 2024 04:44:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6jWp-009EzU-U8 for pgsql-bugs@lists.postgresql.org; Fri, 01 Nov 2024 04:44:56 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6jWj-003tp9-9d for pgsql-bugs@lists.postgresql.org; Fri, 01 Nov 2024 04:44:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 4A14iZve1624906; Fri, 1 Nov 2024 00:44:35 -0400 From: Tom Lane To: Thomas Munro cc: Heikki Linnakangas , =?UTF-8?Q?Bastien_Roucari=C3=A8s?= , pgsql-bugs@lists.postgresql.org Subject: Re: Detection of hadware feature => please do not use signal In-reply-to: References: <4496616.iHFcN1HehY@portable-bastien> <1156374.1730396928@sss.pgh.pa.us> <7ec1c65c-1a28-49a7-af43-f77c260a3df6@iki.fi> <1292593.1730399134@sss.pgh.pa.us> Comments: In-reply-to Thomas Munro message dated "Fri, 01 Nov 2024 17:28:53 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1624904.1730436275.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 01 Nov 2024 00:44:35 -0400 Message-ID: <1624905.1730436275@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > On Fri, Nov 1, 2024 at 7:25 AM Tom Lane wrote: >> It occurs to me to wonder whether the existing code works on Windows. >> Windows-on-ARM wasn't a thing we thought about in 2018, but it's >> a reasonable target now. > I looked into that[1] and decided that I was going to ignore it > completely, because: > [ oodles o' details ] Hmm. So it seems like we could do this: * Linux, FreeBSD, OpenBSD: do run-time test as recommended * Windows, macOS: assume that supported ARM hardware can do this * anything else: assume no hardware CRC The only thing I'd be even a bit sad about there is not having NetBSD support. Maybe we just need to research that a bit more, or maybe we have to wait for/lobby for them to do what the other BSDen have done. But in any case I'm not seeing NetBSD-on-ARM as a platform that's important enough to block movement on this, let alone anything else in the "anything else" category. An alternative to "assume no hardware CRC" could be * anything else: use the existing SIGILL test But I do sympathize with Bastien's concerns about that. regards, tom lane