Re: headerscheck ccache support

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-11-28T14:16:47Z
Lists: pgsql-hackers
On 2025-Nov-28, Peter Eisentraut wrote:

> But this doesn't seem to buy very much.  The overhead of the shell script to
> write out the test files appears to become significant compared the the
> actual compile commands.

If you wanted to save some shell execution time, you could move the `tr`
calls to the bottom of the loop to avoid doing it for files that the
`if` block is going to discard.  But is that significant?  I doubt it.

(I didn't quite understand why you use printf instead of echo, given
that both are shell builtins in any case.)

I think parallelism is also going to win in the case where the compiles
are not cached.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. ci: Run headerscheck and cpluspluscheck in parallel

  2. headerscheck ccache support

  3. headerscheck: Use LLVM_CPPFLAGS