Re: meson vs. llvm bitcode files - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: meson vs. llvm bitcode files
Date
Msg-id CAN4CZFO0XdH+9BZRLC4P=+zCZ3WUvkwGMc0jEV92CfPaU0ePpw@mail.gmail.com
Whole thread
In response to Re: meson vs. llvm bitcode files  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: meson vs. llvm bitcode files
List pgsql-hackers
> I couldn't reproduce this. There are 43 .bc files and header change (I
> changed simd.h) triggers a recompilation of only 'postgres.index.bc'
> on my end. This behavior seems correct to me. Could you please share
> steps to reproduce the behavior you saw?

I can reliably reproduce it on multiple computers.

patch applied on top of 009833ef2002430b1f8fae3a8e47718642b7a5d9,
default meson build with only -Dllvm=enabled

both on ubuntu 24.04/openSUSE tumbleweed with meson 1.3.2, ninja 1.11.1/1.13.2

ninja # to ensure I built everything
ninja # nothing happens, up to date

touch ../src/include/port/simd.h && time ninja -j$(nproc) 2>&1
[884/884] Generating src/backend/jit/llvm/bitcode/postgres with a custom command
ninja -j$(nproc) 2>&1  188.04s user 31.36s system 4541% cpu 4.831 total

touch ../src/include/port/simd.h && ninja -j$(nproc) 2>&1 -n | grep bc | wc -l
796



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: dshash_find_or_insert vs. OOM
Next
From: Andres Freund
Date:
Subject: Re: Don't synchronously wait for already-in-progress IO in read stream