From owner-freebsd-bugs@FreeBSD.ORG Mon Sep 13 01:01:03 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22EA716A5AC for ; Mon, 13 Sep 2004 01:01:03 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1566243D41 for ; Mon, 13 Sep 2004 01:01:03 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8D10xpw057338 for ; Mon, 13 Sep 2004 01:00:59 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8D10xDG057337; Mon, 13 Sep 2004 01:00:59 GMT (envelope-from gnats) Date: Mon, 13 Sep 2004 01:00:59 GMT Message-Id: <200409130100.i8D10xDG057337@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Dan Lukes Subject: Re: bin/71628: [PATCH] cleanup of the usr.sbin/rpcbind code X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dan Lukes List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2004 01:01:03 -0000 The following reply was made to PR bin/71628; it has been noted by GNATS. From: Dan Lukes To: Giorgos Keramidas Cc: alfred@freebsd.org, bug-followup@freebsd.org Subject: Re: bin/71628: [PATCH] cleanup of the usr.sbin/rpcbind code Date: Mon, 13 Sep 2004 02:57:20 +0200 (CEST) On Sun, 12 Sep 2004, Giorgos Keramidas wrote: > He's probably the best person to suggest a fix for this warning, if one > is really needed. There is no need for fix a error as there are no error. The 'fd' is correctly initialized with no exception, althought GCC can't evaluate it. It's try to eliminate unnecesarry warning. > No. I don't know why you think that this is a good fix for all the > uninitialized pointer warnings. It's not. Never :-/ Why ? It's written within the "description" section of the PR. Warning shoult be "attention marks" - THIS CONSTRUCT SHOULD BE REVIEWED. If there are too many warnings related to correct code we can't use it for it purpose. Warnings become notice with almost no value. Well. I compiled the code and evaluate that hundreds of warnings didn't point to problematic code, but are "false" only. I will compile the code next month. Do you think I recognise there are hundreds + 1 warning, so we should evaulate this +1 warning to be sure there are no error ? Warnings may be very usefull information, unless they lie so much. Current code cause piles of false warnings. It "warnings" are hard to use as true warning ... But any commiter can close all of my PR if he think I'm not true ... > After a quick glance at the source of rpcbind() I think that there's no way > that my_xrpt can be used uninitialized. A proper fix for this warning > would be then to just set my_xrpt to NULL at first and let the rest of the > function unchanged regarding my_xrpt. The unnecesarry initialisation of variable initialised again later seems to be vaste of resources. But IMHO only.