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 1uZv44-00AEuo-UV for pgsql-committers@arkaria.postgresql.org; Thu, 10 Jul 2025 17:28:08 +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 1uZv40-00FHqn-Qv for pgsql-committers@arkaria.postgresql.org; Thu, 10 Jul 2025 17:28:05 +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 1uZv40-00FHqf-Jb for pgsql-committers@lists.postgresql.org; Thu, 10 Jul 2025 17:28:05 +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.96) (envelope-from ) id 1uZv3z-006sVx-0B for pgsql-committers@lists.postgresql.org; Thu, 10 Jul 2025 17:28:04 +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 56AHRx2o1604721; Thu, 10 Jul 2025 13:27:59 -0400 From: Tom Lane To: Jacob Champion cc: Michael Paquier , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Fix up misuse of "volatile" in contrib/xml2. In-reply-to: References: <1141878.1752076195@sss.pgh.pa.us> Comments: In-reply-to Jacob Champion message dated "Thu, 10 Jul 2025 10:21:51 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1604719.1752168479.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 10 Jul 2025 13:27:59 -0400 Message-ID: <1604720.1752168479@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jacob Champion writes: > On Wed, Jul 9, 2025 at 8:55=E2=80=AFPM Michael Paquier wrote: >> On Wed, Jul 09, 2025 at 11:49:55AM -0400, Tom Lane wrote: >>> Not sure. Yesterday I saw such warnings from arowana, >>> boa, dhole, rhinoceros, and shelduck, eg >> They are all using some gcc 4.X flavor, most with -O2 but not all. > I think I remember that GCC has had historical problems with tuning > the false-positive:false-negative rates for `-Wmaybe-uninitialized`. > It's not super surprising to me that later versions aren't always > better at seeing specific problems, especially if users were > complaining that an earlier version was too sensitive... Yeah. Worth noting also is that even the machines that were complaining were warning about just a subset of the xpath.c functions that had this problem :-(. So there's definitely some heuristics involved, which seems odd for what feels like it ought to be a pretty black-and-white condition. regards, tom lane