Re: [PATCH] Add loongarch native checksum implementation. - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [PATCH] Add loongarch native checksum implementation.
Date
Msg-id CAA4eK1LsV3KuyUt8tzZDjPcUds1XfVVeW3Wpeju_59DtRV0=xQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Add loongarch native checksum implementation.  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: [PATCH] Add loongarch native checksum implementation.
List pgsql-hackers
On Thu, Aug 10, 2023 at 10:35 AM John Naylor
<john.naylor@enterprisedb.com> wrote:
>
> On Tue, Aug 8, 2023 at 2:22 PM YANG Xudong <yangxudong@ymatrix.cn> wrote:
> >
> > On 2023/8/8 14:38, John Naylor wrote:
> >
> > > v4 0001 is the same as v3, but with a draft commit message. I will
> > > squash and commit this week, unless there is additional feedback.
> >
> > Looks good to me. Thanks for the additional patch.
>
> I pushed this with another small comment change. Unfortunately, I didn't glance at the buildfarm beforehand -- it
seemsmany members are failing an isolation check added by commit fa2e87494, including both loongarch64 members. I'll
checkback periodically. 
>
> https://buildfarm.postgresql.org/cgi-bin/show_status.pl
>

In MSVC build, on doing: perl mkvcbuild.pl after this commit, I am
facing the below error:
Generating configuration headers...
undefined symbol: USE_LOONGARCH_CRC32C at src/include/pg_config.h line
718 at ../postgresql/src/tools/msvc/Mkvcbuild.pm line 872.

Am I missing something or did the commit miss something?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: tender wang
Date:
Subject: [question] multil-column range partition prune
Next
From: Matthias van de Meent
Date:
Subject: Re: [question] multil-column range partition prune