Re: Broken ./configure checks for __cpuid() and __cpuidex()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Broken ./configure checks for __cpuid() and __cpuidex()
Date: 2025-07-29 03:40:17
Message-ID: 808803.1753760417@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> /usr/share/mingw-w64/include/psdk_inc/intrin-impl.h:2013:42: error:
> macro "__cpuid" requires 5 arguments, but only 2 given

Yeah, surely that's broken ...

> How isn't that a bug in MinGW itself? I'm puzzled my the macro
> definition of __cpuid() that reports a conflict. __cpuidex() and
> __cpuid() are both detected by ./configure, the PG use of __cpuid() in
> pg_crc32c_sse42_choose.c causes a failure.

Why is the configure probe succeeding? Maybe pg_crc32c_sse42_choose.c
is including something the configure check isn't?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lukas Fittl 2025-07-29 03:53:43 Re: Broken ./configure checks for __cpuid() and __cpuidex()
Previous Message David Rowley 2025-07-29 03:25:50 Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment