From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Xing Guo <higuoxing(at)gmail(dot)com>, Devrim Gündüz <devrim(at)gunduz(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Mark Wong <markwkm(at)gmail(dot)com>, tcook(at)blackducksoftware(dot)com |
Subject: | Re: Guiding principle for dropping LLVM versions? |
Date: | 2023-11-04 16:38:18 |
Message-ID: | 20231104163818.lxdhufvqgzahzvb4@awork3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2023-11-02 10:46:52 +1300, Thomas Munro wrote:
> So it sounds like we're in agreement that it is time to require LLVM
> 10+ in master. Could the owners (CC'd) of the following animals
> please turn off --with-llvm on master (and future 17+ branches), or
> consider upgrading to a modern OS release? Otherwise they'll turn
> red.
>
> And of course Andres would need to do the same for his coverage
> animals in that range:
>
> animal | arch | llvm_version | os | os_release
> | end_of_support
> -------------+--------------------+--------------+--------+------------+----------------
> dragonet | x86_64 | 3.9.1 | Debian | sid |
> phycodurus | x86_64 | 3.9.1 | Debian | sid |
> desmoxytes | x86_64 | 4.0.1 | Debian | sid |
> petalura | x86_64 | 4.0.1 | Debian | sid |
> idiacanthus | x86_64 | 5.0.2 | Debian | sid |
> pogona | x86_64 | 5.0.2 | Debian | sid |
> komodoensis | x86_64 | 6.0.1 | Debian | sid |
> xenodermus | x86_64 | 6.0.1 | Debian | sid |
Would you want me to do this now or just before you apply the patch?
I think I should stand up a few more replacement animals to cover older llvm
versions with assertions enabled...
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Atharva Bhise | 2023-11-04 16:47:13 | Introduction and Inquiry on Beginner-Friendly Issues |
Previous Message | Bharath Rupireddy | 2023-11-04 15:25:00 | Re: Improve WALRead() to suck data directly from WAL buffers when possible |