| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Matthew Sterrett <matthewsterrett2(at)gmail(dot)com> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Stepan Neretin <slpmcf(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, "Devulapalli, Raghuveer" <raghuveer(dot)devulapalli(at)intel(dot)com>, "Shankaran, Akash" <akash(dot)shankaran(at)intel(dot)com> |
| Subject: | Re: Proposal for enabling auto-vectorization for checksum calculations |
| Date: | 2025-06-02 12:11:45 |
| Message-ID: | CANWCAZb=CDRMMERC7FA=-0mN4hQkToSsPHgBnAV3X1bz=8ONuQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 23, 2025 at 4:54 AM Matthew Sterrett
<matthewsterrett2(at)gmail(dot)com> wrote:
> Okay, I've determined that versions of LLVM/Clang before 19 crash when
> compiling this patch for some reason; it seems that both make
> check-world and make install will crash with the affected LLVM
> versions.
> Unfortunately, what matters seems to be the version of the linker/LTO
> optimizer, which I don't think we can check at compile time.
> I added a check for Clang>=19 which works at preventing the crash on my system.
> I think it's possible some unusual combination of clang/LLVM might
> still crash during the build, but I think this is a reasonable
> solution
I don't know if this is related to the crashes, but it doesn't seem
like a good idea to #include the function pointer stuff everywhere,
that should probably go into src/port like the others.
--
John Naylor
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2025-06-02 12:35:42 | Re: [PING] fallocate() causes btrfs to never compress postgresql files |
| Previous Message | Amit Kapila | 2025-06-02 11:53:43 | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly |