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 1vuyZZ-00FLay-1B for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Feb 2026 19:59:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vuyZX-003GL4-38 for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Feb 2026 19:59:55 +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 1vuyZX-003GKv-2H for pgsql-hackers@lists.postgresql.org; Tue, 24 Feb 2026 19:59:55 +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 1vuyZU-000000010az-3CaH for pgsql-hackers@lists.postgresql.org; Tue, 24 Feb 2026 19:59: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 61OJxlC34014993; Tue, 24 Feb 2026 14:59:47 -0500 From: Tom Lane To: John Naylor cc: Zsolt Parragi , PostgreSQL Hackers , root , Nathan Bossart Subject: Re: centralize CPU feature detection In-reply-to: References: Comments: In-reply-to John Naylor message dated "Mon, 23 Feb 2026 22:32:50 +0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4014991.1771963187.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 24 Feb 2026 14:59:47 -0500 Message-ID: <4014992.1771963187@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk John Naylor writes: > I've committed 0001. BF animal rhinoceros isn't happy. I can reproduce that locally by doing $ ./configure ... USE_SLICING_BY_8_CRC32C=3D1 $ make ... pg_cpu_x86.c: In function 'pg_comp_crc32c_choose': pg_cpu_x86.c:85:3: error: 'pg_comp_crc32c' undeclared (first use in this f= unction); did you mean 'pg_comp_crc32c_sb8'? pg_comp_crc32c =3D pg_comp_crc32c_sse42; ^~~~~~~~~~~~~~ pg_comp_crc32c_sb8 pg_cpu_x86.c:85:3: note: each undeclared identifier is reported only once = for each function it appears in pg_cpu_x86.c:85:20: error: 'pg_comp_crc32c_sse42' undeclared (first use in= this function); did you mean 'pg_comp_crc32c_sb8'? pg_comp_crc32c =3D pg_comp_crc32c_sse42; ^~~~~~~~~~~~~~~~~~~~ pg_comp_crc32c_sb8 pg_cpu_x86.c:108:9: warning: implicit declaration of function 'pg_comp_crc= 32c'; did you mean 'pg_comp_crc32c_sb8'? [-Wimplicit-function-declaration] return pg_comp_crc32c(crc, data, len); ^~~~~~~~~~~~~~ pg_comp_crc32c_sb8 It appears that if you want to build pg_cpu_x86.o unconditionally, you need to make it more proof against the cases it wasn't getting built in before. regards, tom lane