From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: new buildfarm with gcc & clang "trunk" -Werror? |
Date: | 2018-03-28 21:53:30 |
Message-ID: | 4349d6bd-79c3-83d2-56d9-a180942f6bf3@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/28/18 04:06, Fabien COELHO wrote:
> Would the project feel appropriate to:
>
> - fix these warnings (other than putting -Wno-format-truncation or
> similar workarounds...).
I've been tracking gcc-8, and I have a patch ready, but these things
change a bit with every compiler snapshot, so I'm waiting until things
settle down.
> - add permanent gcc/clang trunk beasts with -Werror
> (if so, I'd suggest cannonball & seanettle for the names).
I would not like that. The build farm success should ideally be a
function of correct PostgreSQL code, not external factors. If an
in-progress compiler does funny things, what are we supposed to do about
that?
Generally, fixing up PostgreSQL for a new compiler release isn't a major
effort and can be done briefly before the release of the compiler.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-03-28 21:54:03 | Re: [HACKERS] [PATCH] Vacuum: Update FSM more frequently |
Previous Message | Andres Freund | 2018-03-28 21:31:49 | Re: JIT compiling with LLVM v12 |