| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Clang optimiser vs preproc.c |
| Date: | 2023-12-19 04:20:39 |
| Message-ID: | CA+hUKGJwBi5PFUpcDAi1+YvAoQQG+fuMz=QgQDiFPbgPq7UH0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 19, 2023 at 11:42 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Hrmph. Well something weird is going on, but it might indeed involve
> me being confused about debug options of the compiler itself. How can
> one find out which build options were used for clang/llvm compiler +
> libraries? My earlier reports were from a little machine at home, so
> let's try again on an i9-9900 CPU @ 3.10GHz (a bit snappier) running
> Debian 12, again using packages from apt.llvm.org:
>
> 17 ~198s
> 16 ~14s
> 15 ~11s
And on another Debian machine (this time a VM) also using apt.llvm.org
packages, the huge ~3 minute time occurs with clang-16... hrrrnnnff...
seems like there must be some other variable here that I haven't
spotted yet...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-12-19 04:21:02 | Re: Add a perl function in Cluster.pm to generate WAL |
| Previous Message | Nathan Bossart | 2023-12-19 04:00:29 | Re: WAL Insertion Lock Improvements |