This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: fileops.c:1618: warning: weak declaration of `_IO_do_write' afterfirst use results in unspecified behavior

From: Roland McGrath <roland at redhat dot com>
To: Andreas Jaeger <aj at suse dot de>
Cc: GNU libc hacker <libc-hacker at sources dot redhat dot com>
Date: Fri, 23 Aug 2002 05:46:11 -0400 (EDT)
Subject: Re: fileops.c:1618: warning: weak declaration of `_IO_do_write' afterfirst use results in unspecified behavior

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.

Now the only spurious warnings in my build are "declared static but never
defined" for the things defined in asm and referenced via C decls.  I don't
know of any way to get rid of those.

Follow-Ups:
- Re: fileops.c:1618: warning: weak declaration of `_IO_do_write'after first use results in unspecified behavior
  - From: Andreas Jaeger
- Re: fileops.c:1618: warning: weak declaration of `_IO_do_write'after first use results in unspecified behavior
  - From: Andreas Jaeger

References:
- fileops.c:1618: warning: weak declaration of `_IO_do_write' afterfirst use results in unspecified behavior
  - From: Andreas Jaeger

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]