Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d663F-0005ns-Hz for pgsql-hackers@arkaria.postgresql.org; Thu, 04 May 2017 01:59:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d663E-0006Ze-Hf for pgsql-hackers@arkaria.postgresql.org; Thu, 04 May 2017 01:59:28 +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 1d663D-0006YX-IT for pgsql-hackers@postgresql.org; Thu, 04 May 2017 01:59:27 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d6639-00068u-UR for pgsql-hackers@postgresql.org; Thu, 04 May 2017 01:59:26 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2C7EF208C7 for ; Wed, 3 May 2017 21:59:22 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 03 May 2017 21:59:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=ygT+PLYhIguntkCJWvQXCT53z/Fzl1muZF9V1noKYOE=; b=k3UUj+3B 4pRq/18DUWm22lCr7rzzPul+sE72iJOBMVKkYN+i62C6oqKXmNSAevudiCHmDUAF /NijsS0SFYn1VzbKxi5YHbhnY7Pan8J5Ix6helP228I4vNjq7A0gkMX68p0/JP5O Ks+po+THmsflbgf+i34QJdMq3b1Y3b4MTyr5S+O6b3Zve15+MOEMZ/uMp2vBWpj+ 1PbgDjmUus0pAaTIo4JHcVj08m1JUMKP4hcwI3s3248qKbiz5OA9bb8vkN6WaHJD NBJHsv4OskiJksQx8qQQGKzAePmQ3dPHmSeX2QfZbR7flUQGrmCQ2fsa5EdPe2jm 2vNxjfKi2MrLZw== X-ME-Sender: X-Sasl-enc: xDjXcNMs++rWVCPYYUN6sRijDg5qO2JbGI4nGXjD//T8 1493863162 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id E76CE7E316 for ; Wed, 3 May 2017 21:59:21 -0400 (EDT) Subject: Re: GCC 7 warnings To: pgsql-hackers References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 3 May 2017 21:59:21 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 On 4/10/17 11:03, Peter Eisentraut wrote: > The release of GCC 7 is approaching [0], and the number of warnings in > PostgreSQL has gone up since we last looked [1]. Output attached. (My > version is 7.0.1 20170408.) GCC 7 has been released. Should we backpatch these warning fixes? The commit in question is 6275f5d28a1577563f53f2171689d4f890a46881. (I haven't actually checked whether backpatches well.) PG 9.2 and newer compile warning-free with GCC 6, so there would be some value in preserving this with GCC 7. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers