From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18561 invoked by alias); 23 Aug 2002 10:03:18 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 18545 invoked from network); 23 Aug 2002 10:03:17 -0000 Received: from unknown (HELO Cantor.suse.de) (213.95.15.193) by sources.redhat.com with SMTP; 23 Aug 2002 10:03:17 -0000 Received: from Hermes.suse.de (Charybdis.suse.de [213.95.15.201]) by Cantor.suse.de (Postfix) with ESMTP id 06961144E7; Fri, 23 Aug 2002 12:03:17 +0200 (MEST) Received: from aj by arthur.inka.de with local (Exim 3.34 #1) id 17iBGT-0007Ra-00; Fri, 23 Aug 2002 12:02:01 +0200 Mail-Copies-To: never To: Roland McGrath Cc: GNU libc hacker Subject: Re: fileops.c:1618: warning: weak declaration of `_IO_do_write' after first use results in unspecified behavior References: <20020823094611.E775B1BA1B@perdition.linnaean.org> From: Andreas Jaeger Date: Fri, 23 Aug 2002 03:03:00 -0000 In-Reply-To: <20020823094611.E775B1BA1B@perdition.linnaean.org> (Roland McGrath's message of "Fri, 23 Aug 2002 05:46:11 -0400 (EDT)") Message-ID: User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Artificial Intelligence, i386-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00139.txt.bz2 Roland McGrath writes: > Those warnings have been appearing for a while now (I also see them with > the RH variant of gcc-3.2), but I was too lazy to look into avoiding them > until you spurred me. I was able to get rid of those warnings just by > reordering the decls in those files. The weak decls don't need to appear > before any other decl of the symbol, only before any reference in a > function or another initializer. I see now these warnings (at a different place!): hooks.c:43: warning: weak declaration of `__malloc_initialize_hook' after first use results in unspecified behavior hooks.c:45: warning: weak declaration of `__free_hook' after first use results in unspecified behavior hooks.c:47: warning: weak declaration of `__malloc_hook' after first use results in unspecified behavior The fileops warnings are gone, Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj