From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Problems with --enable-gcc-warnings Date: Tue, 17 Dec 2013 23:08:02 +0200 Message-ID: <83fvprchjh.fsf@gnu.org> References: <83ppovcqcf.fsf@gnu.org> <52B0B8BF.9020409@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1387315737 5097 80.91.229.3 (17 Dec 2013 21:28:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 17 Dec 2013 21:28:57 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 17 22:28:59 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Vt2CF-0000ze-0e for ged-emacs-devel@m.gmane.org; Tue, 17 Dec 2013 22:28:55 +0100 Original-Received: from localhost ([::1]:35713 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt2CE-0003EQ-H8 for ged-emacs-devel@m.gmane.org; Tue, 17 Dec 2013 16:28:54 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34300) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt1rv-0004le-OX for emacs-devel@gnu.org; Tue, 17 Dec 2013 16:08:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vt1rq-0006N2-DC for emacs-devel@gnu.org; Tue, 17 Dec 2013 16:07:55 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:64167) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vt1rq-0006Mh-4a for emacs-devel@gnu.org; Tue, 17 Dec 2013 16:07:50 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MXY00C00YOC5200@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Tue, 17 Dec 2013 23:07:48 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MXY00B9EYP0LQH0@a-mtaout20.012.net.il>; Tue, 17 Dec 2013 23:07:48 +0200 (IST) In-reply-to: <52B0B8BF.9020409@cs.ucla.edu> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:166560 Archived-At: > Date: Tue, 17 Dec 2013 12:49:03 -0800 > From: Paul Eggert > CC: emacs-devel@gnu.org > > On 12/17/2013 09:57 AM, Eli Zaretskii wrote: > > it seems like older compilers have trouble with some of the > > warning options. > > Yes, --enable-gcc-warnings is currently not supported for older GCC > releases. We've found it's enough of a pain keeping it working for > relatively-recent releases. Currently I suspect it really needs 4.6 > or later; maybe even 4.7. Since it's a build-time option, we have > been suggesting to simply not use it if your compiler's old. How about some warning for older GCCs, or maybe even refusing to turn on the compiler warnings in that case? > > Then I had a warning in lib/file-has-acl.c, because under some > > conditions the acl_access_nontrivial doesn't return a value (look near > > its end). > > I tried to fix that in trunk bzr 115573. Thanks. > > Lastly, the INT_BUFSIZE_BOUND macro seems to be unable to support > > 'void *' as its argument without emitting warnings, I need to use > > intptr_t instead to pacify the compiler. > > That's expected; the argument of INT_BUFSIZE_BOUND must be an integer > type or expression. This info is in the prefatory comment. OK, thanks.