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.96) (envelope-from ) id 1wLLfa-001ili-14 for pgsql-hackers@arkaria.postgresql.org; Fri, 08 May 2026 13:55:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wLLfW-009dcg-37 for pgsql-hackers@arkaria.postgresql.org; Fri, 08 May 2026 13:55:06 +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.96) (envelope-from ) id 1wLLfW-009dcX-2C for pgsql-hackers@lists.postgresql.org; Fri, 08 May 2026 13:55:06 +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.98.2) (envelope-from ) id 1wLLfS-00000000ooA-2oNJ for pgsql-hackers@postgresql.org; Fri, 08 May 2026 13:55:04 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 648DstTl961465; Fri, 8 May 2026 09:54:55 -0400 From: Tom Lane To: John Naylor cc: Tobias Bussmann , Lukas Fittl , Jakob Egger , pgsql-hackers , Andres Freund Subject: Re: Broken build on macOS (Universal / Intel): cpuid instruction not available In-reply-to: References: <223EA201-A0E8-4A13-B220-EB903E8DF817@eggerapps.at> <871806.1778168884@sss.pgh.pa.us> <873909.1778170924@sss.pgh.pa.us> <471E4CB3-1690-4168-9A99-5F83D97C12AF@gmx.net> Comments: In-reply-to John Naylor message dated "Fri, 08 May 2026 17:04:15 +0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <961463.1778248495.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 08 May 2026 09:54:55 -0400 Message-ID: <961464.1778248495@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk John Naylor writes: > On Fri, May 8, 2026 at 3:26 PM Tobias Bussmann wrote: >> analysed how useful these universal builds are given the lack of >> optimisations for one of the architectures, but at least they are possible >> again, as they were previously. > Taking a quick look at the configure output you provided, certain > optimizations will be lacking on both architectures: Yeah. I think the main practical problem will be the lowest-common-denominator CRC code. However, AFAICS a universal build would have been selecting that from day one, so if the performance has been acceptable so far it won't be any worse in v19. regards, tom lane