On Fri, Feb 4, 2022 at 8:12 AM Andres Freund <and...@anarazel.de> wrote: > On 2022-02-03 10:44:11 +0100, Fabien COELHO wrote: > > For these reasons, I'm inclined to let seawasp as it is.
It might be easier to use the nightly packages at https://apt.llvm.org/. You could update daily and still save so much CPU that ... > I find seawasp tracking the development trunk compilers useful. Just not for > --with-llvm. The latter imo *reduces* seawasp's, because once there's an API > change we can't see whether there's e.g. a compiler codegen issue leading to > crashes or whatnot. > > What I was proposing was to remove --with-llvm from seawasp, and have a > separate animal tracking the newest llvm release branch (I can run/host that > if needed). ... you could do a couple of variations like that ^ on the same budget :-) FWIW 14 just branched. Vive LLVM 15.
