From owner-freebsd-current@FreeBSD.ORG Mon Jul 21 10:13:05 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id DEDEA37B40B; Mon, 21 Jul 2003 10:13:05 -0700 (PDT) Date: Mon, 21 Jul 2003 10:13:05 -0700 From: David O'Brien To: Harti Brandt Message-ID: <20030721101305.A35445@hub.freebsd.org> References: <7madbg60b1.wl@black.imgsrc.co.jp> <20030715075429.M34004@beagle.fokus.fraunhofer.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030715075429.M34004@beagle.fokus.fraunhofer.de>; from brandt@fokus.fraunhofer.de on Tue, Jul 15, 2003 at 07:59:43AM +0200 X-Operating-System: FreeBSD 4.8-RC Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: Current Subject: Re: src/bin/ed/re.c: warning: declaration of `exp' shadows a global declaration X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 17:13:06 -0000 On Tue, Jul 15, 2003 at 07:59:43AM +0200, Harti Brandt wrote: > On Tue, 15 Jul 2003, Jun Kuriyama wrote: > JK>With new gcc and -Wshadow, src/bin/ed/re.c shows this warning: > JK> > JK>cc -Wshadow -c re.c > JK>re.c: In function `get_compiled_pattern': > JK>re.c:44: warning: declaration of `exp' shadows a global declaration > JK>:0: warning: shadowed declaration is here > JK> > JK>It seems local variable exp is conflicted with exp(3) declaration. I > JK>don't know what name should be used... > > I would call this a compiler bug. It shouldn't declare exp(3) when you > don't include math.h. As I understand the standard the names in math.h are > only reserved when you include math.h. I remember that an earlier version > of gcc had this bug, that was fixed then. Probably they unfixed it again. > > What's the chance of getting this fixed? There is a discussion on the gcc-patches@gcc.gnu.org mailing list, but they are having a hard time agreeing there is a bug here. FreeBSD's GCC problems have a better chance of getting fixed if those that experience and understand the bug would participate in related discussions on the GCC mailing lists. The Linux and Solaris community has no problem doing this -- for some reason the BSD communities expects the poor guy doing the GCC imports to be the single voice for BSD. :-( -- -- David (obrien@FreeBSD.org)