MIME-Version: 1.0
References: <E1tz8dY-001tOE-31@gemulon.postgresql.org>
 <CANWCAZYRbrAyUG29SyVZdamEaSfX0FG=TuyhMaGyqJhpdTN=vg@mail.gmail.com>
In-Reply-To: 
 <CANWCAZYRbrAyUG29SyVZdamEaSfX0FG=TuyhMaGyqJhpdTN=vg@mail.gmail.com>
From: John Naylor <johncnaylorls@gmail.com>
Date: Mon, 31 Mar 2025 15:07:36 +0700
Message-ID: 
 <CANWCAZbA+sDBdSQFcyp_-1T-r5HKFMbLhjM0uwZWZNZ+T9R85A@mail.gmail.com>
Subject: Re: pgsql: Inline CRC computation for small fixed-length input on x86
To: John Naylor <john.naylor@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org, cookt@blackduck.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CANWCAZbA%2BsDBdSQFcyp_-1T-r5HKFMbLhjM0uwZWZNZ%2BT9R85A%40mail.gmail.com>
Precedence: bulk

On Mon, Mar 31, 2025 at 2:18=E2=80=AFPM John Naylor <johncnaylorls@gmail.co=
m> wrote:

> Hmm, skimmer doesn't like this, and it's one of the animals that
> builds with -msse4.2:
>
> https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=3Dskimmer&d=
t=3D2025-03-31%2007%3A00%3A27&stg=3Dconfigure
>
> "checking which CRC-32C implementation to use... SSE 4.2"
>
>  I'm now looking for clues as to what could be causing the build failure.

Looking at the configure output, I don't see -msee4.2 (or equivalent),
so it shouldn't be reporting that it's targeting SSE 4.2. Maybe it's
using a cached value, and deleting the configure cache would clear
this up? (CC'-d owner)

--=20
John Naylor
Amazon Web Services