Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cO80G-0006aq-96 for pgsql-hackers@arkaria.postgresql.org; Mon, 02 Jan 2017 19:10:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cO80F-0007K9-P0 for pgsql-hackers@arkaria.postgresql.org; Mon, 02 Jan 2017 19:10:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cO7yq-0004WW-Au for pgsql-hackers@postgresql.org; Mon, 02 Jan 2017 19:09:12 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cO7yn-00055f-6R for pgsql-hackers@postgresql.org; Mon, 02 Jan 2017 19:09:11 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v02J950W000678; Mon, 2 Jan 2017 14:09:05 -0500 From: Tom Lane To: Joe Conway cc: Robert Haas , Stephen Frost , "pgsql-hackers@postgresql.org" Subject: Re: Compiler warnings In-reply-to: <21d0ae19-c280-086f-2109-4b1174c74af6@joeconway.com> References: <20161129152102.GR13284@tamriel.snowman.net> <20161206202305.GQ23417@tamriel.snowman.net> <20161206204644.GS23417@tamriel.snowman.net> <21d0ae19-c280-086f-2109-4b1174c74af6@joeconway.com> Comments: In-reply-to Joe Conway message dated "Mon, 02 Jan 2017 10:55:48 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <676.1483384144.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 02 Jan 2017 14:09:05 -0500 Message-ID: <677.1483384145@sss.pgh.pa.us> X-Pg-Spam-Score: -5.1 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Joe Conway writes: > If there is agreement on fixing these warnings, other than the bison > generated warning, I would be happy to do it. I'd also be happy to look > for a fix the bison warning as well if desired, but that should be > handled separately I would think. The bison issue is discussed in https://www.postgresql.org/message-id/flat/E1WpjkB-0003zA-N4%40gemulon.post= gresql.org regards, tom lane --=20 Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers