MIME-Version: 1.0
References: <223EA201-A0E8-4A13-B220-EB903E8DF817@eggerapps.at>
 <871806.1778168884@sss.pgh.pa.us> <873909.1778170924@sss.pgh.pa.us>
 <CAP53PkzLmeNUiNtcOyw62KkD7OzthdCbkwGTyAk+Lu3LKsmOcg@mail.gmail.com>
 <CANWCAZa5TEmjLy0xtBjP9NyuVCJpCOpVkBSzw-fqmH8D9tFzDg@mail.gmail.com>
 <471E4CB3-1690-4168-9A99-5F83D97C12AF@gmx.net>
In-Reply-To: <471E4CB3-1690-4168-9A99-5F83D97C12AF@gmx.net>
From: John Naylor <johncnaylorls@gmail.com>
Date: Fri, 8 May 2026 17:04:15 +0700
Message-ID: 
 <CANWCAZZNu5nLzeeNs8TyC6Xs4HKzHni=yeTqCH7_QNpktR2nMQ@mail.gmail.com>
Subject: Re: Broken build on macOS (Universal / Intel): cpuid instruction not
 available
To: Tobias Bussmann <t.bussmann@gmx.net>
Cc: Lukas Fittl <lukas@fittl.com>, Tom Lane <tgl@sss.pgh.pa.us>,
 Jakob Egger <jakob@eggerapps.at>,
	pgsql-hackers <pgsql-hackers@postgresql.org>,
 Andres Freund <andres@anarazel.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CANWCAZZNu5nLzeeNs8TyC6Xs4HKzHni%3DyeTqCH7_QNpktR2nMQ%40mail.gmail.com>
Precedence: bulk

On Fri, May 8, 2026 at 3:26=E2=80=AFPM Tobias Bussmann <t.bussmann@gmx.net>=
 wrote:
> > Am 08.05.2026 um 05:48 schrieb John Naylor <johncnaylorls@gmail.com>:
> >
> > Jakob and Tobias, how far do you get with the attached, at least for
> > the target x86 case?
>
> thanks! I tried the patch and it fixes the universal build that broke wit=
h
> 16743db (and make check passes for both architectures). It remains to be

Great! I've pushed that fix.

> analysed how useful these universal builds are given the lack of
> optimisations for one of the architectures, but at least they are possibl=
e
> again, as they were previously.

Taking a quick look at the configure output you provided, certain
optimizations will be lacking on both architectures:

checking for _mm_crc32_u8 and _mm_crc32_u32... no
checking for __crc32cb, __crc32ch, __crc32cw, and __crc32cd with CFLAGS=3D.=
.. no
checking for __crc32cb, __crc32ch, __crc32cw, and __crc32cd with
CFLAGS=3D-march=3Darmv8-a+crc+simd... no
checking for __crc32cb, __crc32ch, __crc32cw, and __crc32cd with
CFLAGS=3D-march=3Darmv8-a+crc... no
...
checking which CRC-32C implementation to use... slicing-by-8

But compiler builtins seem to work:

checking for builtin __atomic int32 atomic operations... yes
checking for builtin __atomic int64 atomic operations... yes

--
John Naylor
Amazon Web Services