public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] Include malloc.h in libc/stdlib/aligned_alloc.c
Date: Thu, 18 Feb 2021 01:06:12 +0000 (GMT)	[thread overview]
Message-ID: <20210218010612.127913858031@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=c1a565c3966c7a13a13e2c73b49e4ed4c21f4d0c

commit c1a565c3966c7a13a13e2c73b49e4ed4c21f4d0c
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Tue Feb 16 17:42:01 2021 +0100

    Include malloc.h in libc/stdlib/aligned_alloc.c
    
    Without this, for a bare-iron/simulator target such as cris-elf,
    you'll see, at newlib build time:
    
    /x/gccobj/./gcc/xgcc -B/x/gccobj/./gcc/ <many options elided> -c -o lib_a-aligned_alloc.o \
     `test -f 'aligned_alloc.c' || echo '/y/newlib/libc/stdlib/'`aligned_alloc.c
    /y/newlib/libc/stdlib/aligned_alloc.c: In function 'aligned_alloc':
    /y/newlib/libc/stdlib/aligned_alloc.c:35:10: warning: implicit declaration of function \
     '_memalign_r' [-Wimplicit-function-declaration]
       35 |   return _memalign_r (_REENT, align, size);
          |          ^~~~~~~~~~~

Diff:
---
 newlib/libc/stdlib/aligned_alloc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/newlib/libc/stdlib/aligned_alloc.c b/newlib/libc/stdlib/aligned_alloc.c
index feb22c24b..06b3883cf 100644
--- a/newlib/libc/stdlib/aligned_alloc.c
+++ b/newlib/libc/stdlib/aligned_alloc.c
@@ -28,6 +28,7 @@
 
 #include <reent.h>
 #include <stdlib.h>
+#include <malloc.h>
 
 void *
 aligned_alloc (size_t align, size_t size)


                 reply	other threads:[~2021-02-18  1:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210218010612.127913858031@sourceware.org \
    --to=hp@sourceware.org \
    --cc=newlib-cvs@sourceware.org \
    /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).