From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: New warnings in malloc.c
Date: Mon, 13 Jan 2003 04:59:00 -0000 [thread overview]
Message-ID: <u84r8e5yxv.fsf@gromit.moeb> (raw)
I now get:
malloc.c:1472: warning: static declaration for `_int_malloc' follows non-static
malloc.c:1473: warning: static declaration for `_int_free' follows non-static
malloc.c:1474: warning: static declaration for `_int_realloc' follows non-static
malloc.c:1475: warning: static declaration for `_int_memalign' follows non-static
these come from changing malloc.c but not changing malloc.h. IMO they
should be removed from malloc.h.
Ok to apply the appended patch?
Andreas
2003-01-12 Andreas Jaeger <aj@suse.de>
* malloc/malloc.h: Remove now static only functions.
============================================================
Index: malloc/malloc.h
--- malloc/malloc.h 12 Mar 2002 21:58:54 -0000 1.22
+++ malloc/malloc.h 12 Jan 2003 12:32:23 -0000
@@ -229,13 +229,6 @@ struct malloc_state;
typedef struct malloc_state *mstate;
extern mstate _int_new_arena __MALLOC_P ((size_t __ini_size));
-extern __malloc_ptr_t _int_malloc __MALLOC_P ((mstate __m, size_t __size));
-extern void _int_free __MALLOC_P ((mstate __m, __malloc_ptr_t __ptr));
-extern __malloc_ptr_t _int_realloc __MALLOC_P ((mstate __m,
- __malloc_ptr_t __ptr,
- size_t __size));
-extern __malloc_ptr_t _int_memalign __MALLOC_P ((mstate __m, size_t __alignment,
- size_t __size));
#ifdef __cplusplus
}; /* end of extern "C" */
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2003-01-12 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 4:59 Andreas Jaeger [this message]
2003-01-13 4:59 ` Roland McGrath
2003-01-13 4:59 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u84r8e5yxv.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).