Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJZVT-005cps-BR for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jun 2024 14:08:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJZVP-00Djcu-LJ for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jun 2024 14:08:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJZVP-00DjZt-BM for pgsql-hackers@lists.postgresql.org; Tue, 18 Jun 2024 14:08:16 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJZVO-002IOi-4E for pgsql-hackers@postgresql.org; Tue, 18 Jun 2024 14:08:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 45IE8BLs3595844; Tue, 18 Jun 2024 10:08:11 -0400 From: Tom Lane To: Peter Eisentraut cc: pgsql-hackers Subject: Re: CompilerWarnings task does not catch C++ warnings In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Tue, 18 Jun 2024 09:27:02 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3595842.1718719691.1@sss.pgh.pa.us> Date: Tue, 18 Jun 2024 10:08:11 -0400 Message-ID: <3595843.1718719691@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > The CompilerWarnings task on Cirrus CI does not catch warnings in C++ > code. It tries to make warnings fatal by passing COPT='-Werror', but > that does not apply to C++ compilations. > I suggest that we just add COPT to CXXFLAGS as well. I think passing > -Werror is just about the only reasonable use of COPT nowadays, so > making that more robust seems useful. I don't think there is a need for > a separate make variable for C++ here. +1, but what about the meson side of things? regards, tom lane