public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Seongbae Park (박성배, 朴成培)" <seongbae.park@gmail.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
	"Ian Lance Taylor" <ian@airs.com>,
	 	dj@redhat.com
Subject: [PATCH] libiberty: use void * instead of char * for malloc/realloc declarationn
Date: Thu, 13 Mar 2008 00:41:00 -0000	[thread overview]
Message-ID: <ab3a61990803121741s50cf09d9uf77921e4d255c817@mail.gmail.com> (raw)

Hi libiberty maintainers,

During profiled bootstrap,
malloc/realloc declarations in cplus-dem.c causes a compilation error
during stagefeedback, due to conflicting declaration.
It's not clear to me why stagefeedback libiberty is configured as not
having stdlib.h
but regardless this patch looks like the correct thing to do.
Tested by doing a profiled bootstrap (with another patch I'm about to submit).
Ok for mainline ?

Seongbae

2008-03-12  Seongbae Park <seongbae.park@gmail.com>

        * cplus-dem.c (malloc, realloc): Use void * instead of char *
        as return type.

diff -r acf26548a037 libiberty/cplus-dem.c
--- a/libiberty/cplus-dem.c     Wed Mar 12 17:13:01 2008 +0000
+++ b/libiberty/cplus-dem.c     Wed Mar 12 15:35:06 2008 -0700
@@ -52,8 +52,8 @@ Boston, MA 02110-1301, USA.  */
 #ifdef HAVE_STDLIB_H
 #include <stdlib.h>
 #else
-char * malloc ();
-char * realloc ();
+void * malloc ();
+void * realloc ();
 #endif

 #include <demangle.h>

             reply	other threads:[~2008-03-13  0:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  0:41 Seongbae Park (박성배, 朴成培) [this message]
2008-03-13  3:43 ` Ian Lance Taylor

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=ab3a61990803121741s50cf09d9uf77921e4d255c817@mail.gmail.com \
    --to=seongbae.park@gmail.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ian@airs.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).