Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oC0cW-0004ZG-P7 for pgsql-committers@arkaria.postgresql.org; Thu, 14 Jul 2022 15:19:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oC0cT-0003SW-QJ for pgsql-committers@arkaria.postgresql.org; Thu, 14 Jul 2022 15:19:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oC0cT-0003SN-JZ for pgsql-committers@lists.postgresql.org; Thu, 14 Jul 2022 15:19:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oC0cO-00047n-Ue for pgsql-committers@lists.postgresql.org; Thu, 14 Jul 2022 15:19:13 +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 26EFJ6M02833355; Thu, 14 Jul 2022 11:19:06 -0400 From: Tom Lane To: Peter Eisentraut cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines. In-reply-to: <01214fad-1249-183c-2161-837d8f1c1de0@enterprisedb.com> References: <864b47bd-6e82-2d02-070d-ae5076d8c4c1@enterprisedb.com> <2431300.1657736689@sss.pgh.pa.us> <1b09ac8a-5906-3a52-3763-44a9b2115805@enterprisedb.com> <01214fad-1249-183c-2161-837d8f1c1de0@enterprisedb.com> Comments: In-reply-to Peter Eisentraut message dated "Thu, 14 Jul 2022 16:48:25 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2833353.1657811946.1@sss.pgh.pa.us> Date: Thu, 14 Jul 2022 11:19:06 -0400 Message-ID: <2833354.1657811946@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > It seems that -fkeep-inline-functions is more demanding than what wrasse > is running on. I need the attached patch to get it to build cleanly. Interesting. I'm not entirely clear on which external references cause wrasse to spit up. > I think this would be good to apply so that this method of checking > inline functions is available in the future. +1 regards, tom lane